Information processing apparatus, information processing method, information processing system, and storage medium for storing information processing program

ABSTRACT

There is disclosed an information processing apparatus which is handy for a user. In the information processing apparatus, a user interface of a control program for controlling a peripheral is automatically formed in accordance with a function obtained from the peripheral.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to an information processing apparatuswhich controls peripherals such as a printer, a scanner, a facsimilemachine, a copying machine, and the like via a network, IEEE 1394, andother connection forms and which issues jobs to the peripherals, aninformation processing method, an information processing system, and astorage medium in which an information processing program is stored.

2. Related Background Art

When jobs are issued to a printer, a scanner, a facsimile machine, and acopying machine connected via a network, and the like from a hostcomputer and these peripherals are managed, types or models of theperipherals are grasped beforehand, then peripheral control software(control programs) such as appropriate drivers for the machine types,and the like need to be prepared in the host computer.

SUMMARY OF THE INVENTION

However, in the conventional method of preparing beforehand theperipheral control software (control programs) such as appropriatedrivers and utilities for the machine types, the following problemsexist:

(1) The type and machine type of the peripheral as an operation targetneed to be checked beforehand. Particularly in an environment in which aplurality of peripherals are connected via the network, and theconnected machine types can change from moment to moment, it isdifficult to constantly prepare the peripheral software (controlprograms).

(2) It is difficult to control a plurality of connected peripherals in aunified manner.

(3) By using a network management utility, it can be detected that theperipheral is connected to the network, but it is difficult to specifythe type, for example, to specify whether the connected peripheral is aprinter or a scanner. Particularly, when a multi-function peripheralproviding a plurality of functions with one apparatus is connected tothe network, and the like, types of the provided functions cannot bespecified.

Therefore, an object of the present invention is to provide aninformation processing apparatus, an information processing method, aninformation processing system, and a storage medium with an informationprocessing program stored therein, which are handy.

To attain the above-described object, according to the presentinvention, there is provided an information processing apparatus forcontrolling a peripheral, comprising: obtaining means for obtaining afunction of the peripheral; and control means for automatically forminga user interface of a control program for controlling the peripheral inaccordance with the function obtained by the obtaining means.

To attain the object, according to the present invention, there isprovided an information processing method in an information processingapparatus for controlling a peripheral, comprising the steps of:

obtaining a function from the peripheral; and

automatically forming a user interface of a control program forcontrolling the peripheral in accordance with the obtained function.

To attain the object, according to the present invention, there isprovided a storage medium, in which an information processing programexecuted in an information processing apparatus for controlling aperipheral is stored, the information processing program comprising:obtaining a function from the peripheral; and automatically forming auser interface of a control program for controlling the peripheral inaccordance with the obtained function.

To attain the object, according to the present invention, there isprovided an information processing system provided with a peripheral andan information processing apparatus, comprising: the peripheral having aplurality of functions; obtaining means for obtaining the functions ofthe peripheral; and control means for automatically forming a userinterface of a control program for controlling the peripheral inaccordance with the functions obtained by the obtaining means.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a configuration of a multi-function peripheral(MFP) showing an embodiment of the present invention.

FIG. 2 is a diagram of a system configuration showing the embodiment ofthat present invention.

FIG. 3 is a diagram showing a hard configuration of a controller of MFPshown in FIG. 1.

FIG. 4 is a diagram showing a soft configuration of the controller ofMFP shown in FIG. 1.

FIG. 5 is a diagram showing the soft configuration of the controller ofMFP shown in FIG. 1.

FIG. 6 is a diagram showing the soft configuration of the controller ofMFP shown in FIG. 1.

FIG. 7 is a diagram showing an attribute table of Supervisor 410 shownin FIG. 4.

FIG. 8 is a diagram showing meanings of attribute ID and type ID of theattribute table of FIG. 7.

FIG. 9 is a diagram showing a subaddress to service ID table.

FIG. 10 is a diagram showing meanings of connection type ID of FIG. 9.

FIG. 11 is a diagram showing a service ID to task type table.

FIG. 12 is a diagram showing meanings of task type ID of FIG. 11.

FIG. 13 is a diagram showing a user authentication table.

FIG. 14 is a diagram showing an access control table.

FIG. 15 is a diagram showing a security level.

FIG. 16 is a diagram showing an event setting table.

FIG. 17 is a diagram showing an event format table.

FIG. 18 is a diagram showing an attribute table of a print manager.

FIG. 19 is a diagram showing meanings of attribute ID and type ID of theattribute table shown in FIG. 18.

FIG. 20 is a diagram showing a job table.

FIG. 21 is a diagram showing a job request table.

FIG. 22 is a diagram showing an attribute table of a skin job manager.

FIG. 23 is a diagram showing meanings of attribute ID and type ID of theattribute table shown in FIG. 22.

FIG. 24 is a diagram showing an attribute table of a copy job manager.

FIG. 25 is a diagram showing meanings of attribute ID and type ID of theattribute table shown in FIG. 24.

FIG. 26 is a diagram showing an attribute table of a font manager.

FIG. 27 is a diagram showing meanings of attribute ID and type ID of theattribute table shown in FIG. 26.

FIG. 28 is a diagram showing a font table.

FIG. 29 is a diagram showing an attribute table of a form overlaymanager.

FIG. 30 is a diagram showing meanings of attribute ID and type ID of theattribute table shown in FIG. 29.

FIG. 31 is a diagram showing a form overlay table.

FIG. 32 is a diagram showing an attribute table of a log manager.

FIG. 33 is a diagram showing meanings of attribute ID and type ID of theattribute table shown in FIG. 32.

FIG. 34 is a diagram showing a log table.

FIG. 35 is a diagram showing contents of log data.

FIG. 36 is a diagram showing a log format table.

FIG. 37 is a diagram showing an attribute table of a color profilemanager.

FIG. 38 is a diagram showing meanings of attribute ID and type ID of theattribute table shown in FIG. 37.

FIG. 39 is a diagram showing a color profile table.

FIG. 40 is a diagram showing an attribute table of a printer controller.

FIG. 41 is a diagram showing meanings of attribute ID and type ID of theattribute table shown in FIG. 40.

FIG. 42 is a diagram showing a job queue table.

FIG. 43 is a diagram showing a status of FIG. 42.

FIG. 44 is a diagram showing an attribute table of a scanner controller.

FIG. 45 is a diagram showing meanings of attribute ID and type ID of theattribute table shown in FIG. 44.

FIG. 46 is a diagram showing a structure of a command packet.

FIG. 47 is a flowchart showing a processing of the command packet.

FIG. 48 is a flowchart showing an access processing of the attributetable.

FIG. 49 is a flowchart of a service ID list inquiry processing.

FIG. 50 is a flowchart of a subaddress inquiry processing.

FIG. 51 is a flowchart of an inquiry processing of service ID with adesignated task type.

FIG. 52 is a diagram showing a job structure.

FIG. 53 is a flowchart of a job script processing in each manager.

FIG. 54 is a flowchart of the job script processing in each manager.

FIG. 55 is a flowchart of a job processing in the print job manager.

FIG. 56 is a flowchart of the job processing in the scan job manager.

FIG. 57 is a flowchart of the job processing in the copy job manager.

FIG. 58 is a flowchart of the job processing (download) in the fontmanager, form overlay manager, log manager, and color profile manager.

FIG. 59 is a flowchart of the job processing (upload) in the fontmanager, form overlay manager, log manager, and color profile manager.

FIG. 60 is a flowchart of job management in each manager.

FIG. 61 is a flowchart of event transmission.

FIG. 62 is a flowchart of data (script) transmission from an apparatus.

FIG. 63 is a diagram showing a hard configuration of Client PC.

FIG. 64 is a diagram showing a software (control program) configurationof Client PC.

FIG. 65 is a flowchart of a packet generation/transmission processing.

FIG. 66 is a flowchart of information obtaining and automatic software(control program) forming on the side of Client.

FIG. 67 is a flowchart of job issuance with the designated task type.

FIG. 68 is a diagram showing an event structure.

FIG. 69 is a flowchart of event transmission.

FIG. 70 is a flowchart of a log processing.

FIG. 71 is a flowchart for obtaining/processing charge information.

FIG. 72 is a flowchart of job issuance (print job, data download).

FIG. 73 is a flowchart of the job issuance (scan job, data upload).

FIG. 74 is a flowchart of copy job issuance.

FIG. 75 is a flowchart of job management command issuance.

FIG. 76 is a memory map of DISK 315 of MFP.

FIG. 77 is a memory map of DISK 6009 of Client PC.

FIG. 78 is a diagram showing a configuration of Client PC.

FIG. 79 is a diagram showing LBP applicable to a laser beam printerengine of MFP.

FIG. 80 is a diagram showing IJRA applicable to an ink jet printerengine of MFP.

FIG. 81 is a diagram showing a sample of a display screen displayed on adisplay.

FIG. 82 is a diagram showing a sample of the display screen displayed onthe display.

FIG. 83 is a diagram showing a display of manager list.

FIG. 84 is a diagram showing a display of printer name list.

FIG. 85 is a diagram showing a printer property screen.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Configuration ofMulti-Function Peripheral

FIG. 1 is a diagram of a configuration of a multi-function peripheral(MFP) showing an embodiment of the present invention.

In FIG. 1, a controller 101 for controlling the multi-functionperipheral has a hardware configuration shown in FIG. 3, and has asoftware (control program) configuration shown in DISK 315 of FIG. 76 asa storage medium. A scanner engine 102 is controlled by the controller101. Laser beam printer engines (LBP) 103, 104 are controlled by thecontroller 101. The laser beam printer engine 103 is connected to afinisher 106, so that a plurality of recording media (e.g., paper)outputted from the printer engine can collectively be stapled(Hotchkiss) and processed. The finisher 106 is also controlled by thecontroller 101. An inkjet printer engine (IJP) 105 can also performcolor printing, and is controlled by the controller 101. A network(Ethernet) interface 107 provides the controller 101 with bidirectionalcommunication through the interface. IEEE 1394 interface 108 providesthe controller 101 with bidirectional communication through theinterface. IEEE 1284 interface 109 provides the controller 101 withbidirectional communication through the interface. A user interface 110is constituted of LCD display and a keyboard to display information fromthe controller 101 and to transmit an instruction from a user to thecontroller 101.

For the multi-function peripheral configured as described above, aselection is made from three physical printers LBP 103 (B/W, withFinisher 106), LBP 104 (B/W), and IJP 105 (Color) so that print jobissuance is enabled. Moreover, a selection is made from four logical(cluster) printers LBP 103+LBP 104, LBP 104+IJP 105, LBP 103+IJP 105,LBP 103+LBP 104+IJP 105 so that the print job issuance is enabled.Furthermore, an automatic selection is made from the seven printers LBP103, LBP 104, IJP 105, LBP 103+LBP 104, LBP 104+IJP 105, LBP 103+IJP105, and LBP 103+LBP 104+IJP 105 so that the print job issuance isenabled. Furthermore, IJP is used to constitute a logical printer as aprinter which can print only white and black so that the print job issueis enabled.

Moreover, scan job can be issued from the outside, and a color originalcan be read. Furthermore, a selection is made (automatic selection canalso be made) from the scanner and the eight printers LBP 103, LBP 104,IJP 105, LBP 103+LBP 104, LBP 104+IJP 105, LBP 103+IJP 105, LBP 103+LBP104+IJP 105, and IJP which can print only white and black so that thecopy job can be issued. Furthermore, when only the printer IJP ispresent, color copy job can be issued.

Moreover, font, and form overlay can be used in the print job,upload/download can be realized, and resource management can beperformed. Moreover, color profile can be used in the print job, scanjob, and copy job, upload/download can be realized, and resourcemanagement can be performed. Furthermore, log can automatically begenerated inside the apparatus and upload can be realized.

Moreover, all the functions can be used from any network interface of(Ethernet, TCP/IP), IEEE 1284, and IEEE 1394. Furthermore, eachinterface is associated with a subaddress, physical/logical devices(printer, scanner, copy) and each resource. By selecting the subaddress,these physical/logical devices and each resource can be selected. Toeach subaddress of each interface, the job can be issued anddownload/upload can be instructed at the same time. Moreover, theassociation of the subaddress with the physical/logical device and theresource can be obtained by inquiring of the apparatus itself.Furthermore, the function can be used via an internal user interface.

Moreover, by inquiring of Supervisor described later through theabove-described interface from the outside, the outlines of providedfunctions (a type of job to be issued, a type of resource to beutilized, and the like), job issuance, subaddresses for use indownload/upload of the resources, and detailed information of eachfunction (the maximum number of copy sheets, PDL supporting a finishertype, the number of output BIN to be designated, and the like) can beobtained. By using the above-described information, software (controlprogram) can automatically be formed on the side of Client. However,Client needs to know beforehand only the subaddress for use in theinquiry in each interface. A manager can limit the above-describedvarious functions by the connection form and user.

Entire System Configuration

FIG. 2 is a diagram showing a system configuration of the presentembodiment. In FIG. 2, numeral 201 denotes the multi-function peripheral(MFP) shown in FIG. 1, and the multi-function peripheral 201 isconnected to Client PC's 202 to 205 (information processing apparatuses)via a network interface cable 208 (10 BASE-T), IEEE 1394 interface cable206, and IEEE 1284 interface cable 207, respectively. In each Client PCas shown in FIG. 78, various software (control programs) stored in DISK6009 described later as the storage medium shown in FIG. 77 areoperating. Client PC 202 and 203 connected via Ethernet 208 designate IDaddress and a port number to connect with the multi-function peripheral201, and output IP packet data. Client PC 204 connected via IEEE 1394interface 206 designates a node ID and LUN (logical unit number) toconnect with the multi-function peripheral 201, and outputs SBP-2 packetdata. Client PC 205 connected via IEEE 1284 interface 207 designates asocket number to connect with the multi-function peripheral 201, andoutputs IEEE 1284.4 packet data.

Hardware Configuration of Controller

FIG. 3 is a diagram showing a hardware configuration of the controller101 of the embodiment shown in FIG. 1. Inside the controller 101, CPU301 is connected via a bus 313 to Memory (RAM) 302, LCD display 303 anda keyboard 304 constituting the user interface (operating portion) 110,ROM 314, and DISK 315. Various programs and data shown in FIG. 76 arestored in DISK 315 (storage medium) such as a hard disk, a floppy disk,and the like, sequentially read into Memory (RAM) 302 if necessary, andexecuted by CPU 301. The DISK 315 may be detachably attached to MFP 201or incorporated in MFP 201. Furthermore, the program shown in FIG. 76may be configured to be downloaded from Client PC 202 to 205 or anotherMFP via the network interface cable 208 (10 BASE-T), IEEE 1394 interfacecable 206, and IEEE 1284 interface cable 207 and stored in DISK 315.

The LCD display 303 and the keyboard 304 constitute the user interface(operating portion) 110 shown in FIG. 1. When CPU 301 writes data to LCDdisplay 303, display is performed. When CPU 301 reads data from thekeyboard 304, the instruction from the user is entered.

Moreover, to the bus 313 a network interface connector 305, IEEE 1394interface connector 306, and IEEE 1284 interface connector 307 areconnected, and correspond to the network interface 107, IEEE 1394interface 108, and IEEE 1284 interface 109 shown in FIG. 1,respectively. Then, Ethernet (10 BASE-T) cable 208, IEEE 1394 cable 206,and IEEE 1284 cable 207 shown in FIG. 2 are connected. When CPU 301reads or writes data from or to these interfaces, communication isperformed using the interfaces.

Furthermore, to the bus 313 are connected Laser Beam Printer Engine 308,Finisher 309, Scanner Engine 310, Laser Beam Printer Engine 311, and InkJet Printer Engine 312. These correspond to Laser Beam Printer Engine103, Finisher 106, Scanner Engine 102, Laser Beam Printer Engine 104,and Ink Jet Printer Engine 105 shown in FIG. 1, respectively. When CPU301 performs data reading/writing via these engines, engine operationssuch as printing and scanning are performed and various statuses areobtained. Additionally, Laser Beam Printer Engine 308, Finisher 309,Scanner Engine 310, Laser Beam Printer Engine 311, and Ink Jet PrinterEngine 312 are arranged not inside MFP 201, but are arranged as separateperipheral units on the network, and may be controlled by the controller101 of MFP 201.

Software Configuration of Controller 101

FIG. 4 is a diagram showing a software (control program) configurationof DISK 315 in the controller 101, and the software (control program) isexecuted by CPU 301. In the drawing, solid lines indicate data andcontrol, while dotted lines indicate setting and ability obtaining. Auser interface driver 401 controls LCD display 303 and a keyboard 304. Auser interface manager (control program) 405 interprets inputinformation entered via UI driver 401 from the user, generates a commandpacket shown in FIG. 46, and transmits an output to an interpreter(control program) 409. The user interface manager 405 also interpretsthe command packet entered via the interpreter 409, and performs displayon LCD display 303 via UI driver (control program) 401.

A network interface driver (control program) 402 controls the networkinterface connector 305, and processes a physical layer of networkpacket (physical packet) by extracting a transport packet from thephysical packet and generating the physical packet from the transportpacket. A TCP/IP, UDP/IP processing module 406 processes the transportpacket outputted from the network interface 402, extracts a commandpacket, and transmits an output to the interpreter 409. Moreover, themodule generates the transport packet from the command packet outputtedfrom the interpreter 409, and transmits an output to the networkinterface 402.

IEEE 1284 driver (control program) 403 controls the IEEE 1284 interface307. Numeral 407 denotes a processing module (control program) of IEEE1284.4. IEEE 1284.4 is a standard of a transport layer mainly for thepurpose of being used in IEEE 1284 interface. A processing module(control program) 407 of IEEE 1284.4 processes the transport packetoutputted from the IEEE 1284 driver 403 to extract the command packetand transmits an output to the interpreter 409. Moreover, the modulegenerates the transport packet from the command packet outputted fromthe interpreter 409, and transmits an output to the IEEE 1284 driver403. IEEE 1394 driver (control program) 404 controls the IEEE 1394interface 306.

A module (control program) 408 processes SBP (serial bus protocol)-2which is the transport layer in the IEEE 1394. The SBP-2 processingmodule 408 processes the transport packet outputted from the IEEE 1394driver 404 to extract the command packet and transmits an output to theinterpreter 409. The module also generates the transport packet from thecommand packet outputted from the interpreter 409, and transmits anoutput to the IEEE 1394 driver 404. Numeral 409 denotes a packetinterpreter which interprets the command packets transmitted from thetransport processors 406, 407, 408 and the user interface manager 405and generates commands. The packet interpreter 409 also generates thecommand packet in response to a request from another module (controlprogram). In accordance with a subaddress to service ID table (FIG. 9)of Supervisor (general administration manager) 410, the interpreter 409processes only the command packet transmitted from the subaddress whichis valid, and cancels the command packets transmitted from the othersubaddresses.

Supervisor (general administration manager) 410 retains in DISK 315various data shown in FIG. 7 (attribute table), FIG. 9 (subaddress toservice ID table), FIG. 11 (service ID to task type table), FIG. 13(user authentication table), FIG. 14 (access control table), FIG. 16(event setting table), and FIG. 17 (event format table), and generallymanages an operation of the controller 101. In response to enteredcommand instructions, Supervisor 410 refers to or changes various dataretained by itself, various data retained by managers (font manager 413,form overlay manager 414, log manager 415, color profile manager 416,print managers 501 to 509, scan job manager 419 and copy job managers601 to 608), and various data retained by controllers (printercontrollers 510 to 512, scanner controller 420).

For the command packet interpreted by the interpreter 409, in accordancewith the user authentication table (FIG. 13) and access control table(FIG. 14) of Supervisor 410 (control program), a security gate 411limits a command input in such a manner that only the user who possessesa correct right to use can use the multi-function peripheral 201. Adispatcher (control program) 412 distributes the commands transmittedfrom the interpreter 409 to the resource managers (font manager 413,form overlay manager 414, log manager 415, color profile manager 416)and the job managers (print managers 501 to 509, scan job manager 419and copy job managers 601 to 608) which are control programs forprocessing the commands. The font manager 413 manages fonts. The fontmanager 413 retains data as shown in FIG. 26 (attribute table) and FIG.28 (FONT table) in DISK 315. The font (stored in DISK 315 or ROM 314)managed by the font manager 413 is transferred to PDL rasterizers 417and 418, and used during a print job processing.

The form overlay manager 414 manages form overlays. The form overlaymanager 414 retains data as shown in FIG. 29 (attribute table) and FIG.31 (FORM table) in DISK 315. The form overlay (stored in DISK 315 or ROM314) managed by the form overlay manager 414 is transferred to PDLrasterizers 417 and 418, and used during the print job processing. Thelog manager 415 manages logs. The log manager 415 retains data as shownin FIG. 32 (attribute table) and FIG. 34 (LOG table) in DISK 315. Thelog is outputted from each manager, and placed under control of the logmanager. An execution log file is stored in RAM 302 or DISK 315 andupdated at any time.

The color profile manager 416 manages color profile data for a colorscanner or a color printer to perform color matching. The color profilemanager 416 retains data as shown in FIG. 37 (attribute table) and FIG.39 (color profile table) in DISK 315. Color profiles managed by thecolor profile manager 416 are transferred to the printer controllers(control programs) 510, 511, 512 and the scanner controller (controlprogram) 420, and used during processing of the print job, copy job andscan job. The PDL rasterizer 417 processes document data written in PS(registered trademark) as one type of PDL (page description language),and outputs image data. The PDL rasterizer 418 processes document datawritten in PCL (registered trademark) as one type of PDL (pagedescription language), and outputs image data. The scan job manager 419manages the scan job. The scan job manager 419 retains data as shown inFIG. 22 (attribute table) in DISK 315. The scan job manager 419instructs the scanner controller 420 to execute scanning. The scannercontroller 420 controls the scanner engine 310. The scanner controller420 retains data indicating a function, state and performance of thescanner engine 310 as shown in FIG. 44 (attribute table) in DISK 315.The scan job manager 419 and scanner controller 420 have the dataindicating the functions and performances (FIGS. 22 and 44), but thefunctions shown by these data do not need to be the same. By rewritingthe data (FIG. 22) retained by the scan job manager 419 throughSupervisor 410, the function can be limited.

The above-described font manager 413, form overlay manager 414, logmanager 415, and color profile manager 416 are resource managementprograms, the scan job manager 419, print job managers 501 to 509, thecopy job managers 601 to 608 are logical device (scanner, printer)control programs, and the laser beam printer controllers 510, 511, inkjet printer controller 512, and scanner controller 420 are physicaldevice (printer, scanner) control programs.

Configuration of Print Job Manager

FIG. 5 is a diagram which supplements the software (control program)configuration diagram shown in FIG. 4. Illustrated dispatcher 412 is thesame as the dispatcher 412 shown in FIG. 4, and distributes the commandpackets to the print job managers (control programs) 501 to 509. Theprint job managers 501 to 509 manage the print job. Each print jobmanager has data as shown in FIG. 18 (attribute table) in DISK 315. Foreach print job manager, a printer controller for use in processing theprint job (LBP Controller 510, LBP Controller 511, Ink Jet Controller512, or an arbitrary combination of the controllers 510, 511, 512) and aprint engine connected to the controller are determined, and the type ofprinter controller (control program) to be used is described in datashown by attribute ID 2001 of FIG. 18. However, only the print jobmanager 508 has a function of dynamically selecting the print engine foruse, and it is described in data (attribute table) of the print jobmanager 508 that the manager has the function. Each print managerretains the entered print job, and data indicating the type of printercontroller and the type of job to be executed by the printer controlleras shown in FIG. 20 (job table) and FIG. 21 (job request table) in DISK315. The printer controllers 510 to 512 control the print engines 308,311 and 312. The printer controller 510 also controls the finisher 309.Each printer controller has data indicating a function, state andperformance of the corresponding printer engine as shown in FIG. 40(attribute table) in DISK 315. Each controller retains data indicating astate of entered print job as shown in FIG. 42 (job queue table) in DISK315.

The print job managers 501 to 509 and the printer controllers 510 to 512have data indicating the functions and performances as shown in FIG. 18(attribute table) and FIG. 40 (attribute table) in DISK 315. In generalthe print job manager has a performance equal to a sum of theperformances of the controllers for use, and a function corresponding toa common item of the function of each controller. However, some of thefunctions can be changed by rewriting the data (FIG. 18) of the printjob manager through Supervisor 410. For example, since the print jobmanagers 503 and 509 use the same printer controller 512, they canpresent the same performance and function. However, the data of theprint job managers can be set by a setting processing described later insuch a manner that the print job manager 503 can perform color printingand the print job manager 509 cannot perform the color printing.

Configuration of Copy Job Manager

FIG. 6 is a diagram which supplements the software (control program)configuration diagram shown in FIGS. 4 and 5. This dispatcher 412 is thesame as the dispatcher 412 shown in FIG. 4, and distributes the commandpackets to the copy job managers (control programs) 601 to 608. The copyjob managers 601 to 608 manage the copy job. Each copy job manager hasdata as shown in FIG. 24 (attribute table) in DISK 315. For each copyjob manager, a printer controller and a scanner controller for use inprocessing the copy job and a print engine and a scanner engineconnected to the controllers are determined, and the types of printercontroller and scanner controller to be used are described in the data(attribute ID 2001) shown in FIG. 24. However, only the copy job manager608 has a function of dynamically selecting the print engine for use,and it is described in data (attribute ID 2002) of the copy job manager608 that the manager has the function. Each copy manager holds theentered copy job, and data indicating the type of printer controller orscanner controller and the type of job to be executed by the controlleras shown in FIG. 20 (job table) and FIG. 21 (job request table) in DISK315. The printer controllers 510 to 512 control the print engines, andare the same as those shown in FIG. 5.

Attribute Table of Supervisor

FIG. 7 shows data (attribute table) which Supervisor (control program)410 retains in DISK 315 and manages. This table shows a functionoutline, connection information, security information, and the like ofthe multi-function peripheral 201. In the table, each line shows oneinformation unit (record), and the data is constituted as an aggregateof a plurality of records. Each record is constituted of attribute ID701, type ID 702 and attribute value 703, and indicates an attribute ofSupervisor. The attribute ID 701 indicates a type of information,thereby indicating a meaning of the value 703. The attribute ID 701 isunique inside the apparatus, and the same attribute ID indicates thesame information type. The type ID 702 indicates a type of data whichthe value 703 has, and is used in interpreting the value 703. The typeID is univocally determined by the attribute ID and defined uniquelyinside the apparatus. In the embodiment, the attribute ID 701 and thetype ID 702 are both shown in the attribute table, but by retaining anattribute ID to type ID table as data separated from the attributetable, only the attribute ID and value may be shown in the attributetable. The value 703 indicates an attribute value in accordance with theattribute ID 701.

FIG. 8 is a diagram showing details of attribute ID 701 and type ID 702of the attribute table of FIG. 7. In the drawing, attribute ID 102 “alist of supported security levels” retains a list of security levelswhich can be set, among security levels required for issuing operationfor Supervisor. The security levels will be described in description ofan access control table of FIG. 14. Attribute 103 “current securitylevel” indicates a security level-which is currently set in Supervisor.Attribute ID 401 “current count data” indicates a list of information ascount targets in Supervisor, and its meaning is shown by attribute ID402 “count data format”. For example, count data 45, 78, 34, 13 indicatethe number of print sheets having a paper size shown in the count dataformat. The attribute ID 402 “count data format” is shown as a list ofattribute ID. Since the attribute ID is defined to be unique in theapparatus, by designating the attribute ID, the meaning of the countdata can be designated. For example, an attribute value 565 of attributeID 402 means the number of print sheets with a sheet size of A2, anattribute value 537 means the number of print sheets with a sheet sizeof A3, an attribute value 545 means the number of print sheets with asheet size of A4, and an attribute value 523 means the number of printsheets with a sheet size of A5. Count limit data of attribute ID 403shows a maximum value which the attribute ID 401 “current count data”can have. When even one of the values of “current count data” exceedsthe maximum value, by invalidating a valid flag of the subaddress toservice ID table shown in FIG. 9, CPU 301 invalidates all the services(by the manager). Count unit price data of attribute ID 404 shows a unitprice for every count of the attribute ID retained in the attribute ID402 “count data format” in terms of a currency unit. Current charge dataof attribute ID 405 indicates a value obtained by multiplyingcorresponding values of the attribute ID 401 “current count data” andattribute ID 404 “count unit price data” and taking a sum. Charge limitdata of attribute ID 406 shows a maximum value which the attribute ID405 “current charge data” can have. When the attribute ID 405 “currentcharge data” exceeds an attribute ID 406 “charge limit data”, bychanging a valid flag to an invalid flag in the subaddress to service IDtable shown in FIG. 9, the CPU 301 invalidates all the services (by themanager). A list of supported events of attribute ID 501 shows eventswhich can be set to be notified to Supervisor by a list of event IDwhich is univocally defined for every event type. Actual eventtransmission is set by setting a connection type and addressee of eventnotification with event ID in the event setting table shown in FIG. 16.For the values of the attribute table of FIG. 7, description “TableData” indicates that values (52 to 104) are data each having a tableformat shown by type ID.

Subaddress to Service ID Table

FIG. 9 shows a subaddress to service ID table. This table is retained inDISK 315 as attribute values of an attribute ID 1001 (subaddress to SIDtable) in the attribute table shown in FIG. 7. The subaddress to SIDtable shows a type of service (e.g., print, font download, and the like)obtained by placing the command packet in a subaddress, and thesubaddress. Moreover, in accordance with the valid flag, and the like ofthe table, the interpreter 409 controls each connection form concerningwhether a job service is provided. In the table each line shows oneinformation unit (record), and the data is constituted as an aggregateof a plurality of records. Each record is constituted of a connectiontype ID 801, subaddress 802, service ID 803, valid flag 804, valid userlist 805, and invalid user list 806. The connection type ID 801indicates an identifier indicating the connection form. FIG. 10 is adiagram showing meanings of connection type ID: 0 denotes Internal (userinterface); 1 denotes TCP/IP (network); 2 denotes IEEE 1284.4 (IEEE1284); and 3 denotes SBP-2 (IEEE 1394).

The subaddress 802 shows a subaddress of each connection form. Althoughthe user interface has no subaddress, for the sake of convenience thesubaddress is allocated to the interface, and the command packet isplaced together with subaddress information from the user interface.

The service ID 803 is an identifier indicating a service. The service ID803 is allocated to each manager shown in FIGS. 4, 5 and 6 in one-to-onecorrespondence.

The valid flag 804 shows whether the subaddress is valid. When the valueis true (YES), the subaddress is valid, so that the user can issue thecommand packet to the subaddress. When the value is false (NO), thesubaddress is invalid, which means that even if the command packet istransmitted to the subaddress, the packet is canceled. FIG. 8 shows thatwhen the connection form of connection type ID 2 (IEEE 1284) is used, aservice of service ID 8 (print job manager) cannot be provided.

The valid user list 805 shows a list of user ID which can receive theservice when the subaddress is valid. The invalid user list 806 shows alist of user ID which cannot receive the service even when thesubaddress is valid. The value can be set to only one of the valid userlist 805 and the invalid user list 806.

Service ID to Task Type Table

FIG. 11 shows a service ID to task type table. This table is retained inDISK 315 as attribute values of attribute ID 1002 (SID to Task TypeTable) of the attribute table shown in FIG. 7. The service ID to tasktype table shows the type of service provided by the service ID. In thetable each line shows one information unit (record), and data isconstituted as an aggregate of a plurality of tasks. Each record isconstituted of service ID 901 and task type 902. The task type 902 showsthe type of service. FIG. 12 is a diagram showing meanings of values ofthe task type 902: 0 denotes the service performed by Supervisor; 1denotes print; 2 denotes scan; 3 denotes copy; 101 denotes font; 102denotes form overlay; 103 denotes log; and 104 denotes color profile.Service ID has a one-to-one correspondence with the manager whichprovides the service. Therefore, the service ID can be used foraccessing a function table of each manager. Since each printercontroller or scanner controller also has the function table, in orderto access the table, a controller ID equivalent to the service ID isallocated to the printer controller or the scanner controller, and thetype of controller shown by the controller ID is managed in the serviceID to task type table. A task type 201 denotes a printer controller, and202 denotes a scanner controller. The controller ID has a one-to-onecorrespondence with each controller shown in FIGS. 4 and 5.

Meanings of service ID values are as follows:

0: Supervisor 410

1: print job manager 501

2: print job manager 502

3: print job manager 503

4: print job manager 504

5: print job manager 505

6: print job manager 506

7: print job manager 507

8: print job manager 508

9: print job manager 509

10: scan job manager 419

11: copy job manager 601

12: copy job manager 602

13: copy job manager 603

14: copy job manager 604

15: copy job manager 605

16: copy job manager 606

17: copy job manager 607

18: copy job manager 608

101: font manager 413

102: form overlay manager 414

103: log manager 415

104: color profile manager 416

21: printer controller 510

22: printer controller 511

23: printer controller 512

24: scanner controller 420

User Authentication Table

FIG. 13 shows a user authentication table retained by Supervisor, andshows authentication information of users who can use the apparatus.This table is retained in DISK 315 as attribute values of attribute ID1003 (user authentication table) of the attribute table shown in FIG. 7.The user authentication table shows a set of valid user ID and password,together with information as to whether the user has a managerprivilege. In the table each line shows one information unit (record),and data is constituted as an aggregate of a plurality of records. Eachrecord is constituted of user ID 1001, password 1002 and managerprivilege flag 1003. The manager privilege flag 1003 indicates whetherthe user has a right as a manager.

Access Control Table

FIG. 14 is an access control table retained by Supervisor, and shows asecurity level of each service. This table is retained in DISK 315 asattribute values of attribute ID 1004 (access control table) of theattribute table shown in FIG. 7. The access control table retains thesecurity level necessary for each service ID, and a list of users whoare permitted to be given services. In the table each line shows oneinformation unit (record), and data is constituted as an aggregate of aplurality of records. Each record is constituted of service ID 1101,security level 1102 and user ID list 1103. The security level 1102 showsauthentication information necessary for receiving the servicedesignated by the service ID 1101, that is, for issuing the commandpacket to the manager indicated by the service ID 1101. FIG. 15 showsmeanings of security levels: security level 0 shows that userauthentication is unnecessary; 1 shows that only the manager isdiscriminated; 2 shows that the service is available only for anauthenticated user, but the user ID is used and no password is used forauthentication; and 3 shows that the service is available only for theauthenticated user, and the user ID and password are used for theauthentication. The user ID list 1103 shows a list of user ID permittedto use (access) when the security level 1102 is 2 or 3.

Event Setting Table

FIG. 16 shows an event setting table retained by Supervisor. This tableis retained in DISK 315 as attribute values of attribute ID 502 (eventsetting table) of the attribute table shown in FIG. 7. The event settingtable retains, for each event type, a method of transmitting eventnotification and an addressee when a designated event occurs in theapparatus. In the table each line shows one information unit (record),and data is constituted as an aggregate of a plurality of records. Eachrecord is constituted of an event ID 1201, connection type 1202 andnotification addressee 1203. The addressee is constituted of theconnection type and a notification address dependent on the connectiontype. The event ID 1201 shows an event type, and is defined to be uniquein the apparatus. For example, Event ID 200 indicates that there is nopaper, ID 399 indicates that there is no toner, ID 432 indicates thatthere is no ink, and ID 234 indicates that a cover of the multi-functionperipheral is open. The connection type ID 1202 shows a connection typeby which the event notification is transmitted, and values are the sameas those which are used in the subaddress to service ID table of FIG. 9.The notification addressee 1203 shows event notification addresseessuitable for the connection type 1202.

Event Format Table

FIG. 17 is an event format table retained by Supervisor showing eventcontents. This table is retained in DISK 315 as attribute values ofattribute ID 503 (event format table) of the attribute table shown inFIG. 7. The event format table retains a type of additional datatransmitted as the event notification, for each event ID defined to beunique in the apparatus. In the table each line shows one informationunit (record), and data is constituted as an aggregate of a plurality ofrecords. Each record is constituted of event ID 1301 and event format1302. The event format 1302 is a type of the additional data transmittedas the event notification, and shown as an attribute ID list. Theattribute ID is defined to be unique in the apparatus. Since the type isalso univocally determined by the attribute ID, by designating theattribute ID, a format of the additional data can be shown. For example,an attribute ID 676 of the event format 1302 indicates a paper size, ID756 indicates a paper type, ID 666 indicates a toner type, ID 698indicates an ink type, and ID 600 indicates a cover position. Asdescribed hereinafter, event transmission methods and addressees are setin the data (attribute table) retained by each manager and controller,and the event which occurs in each manager and controller can benotified, but the additional data format of the event is also retainedin the event format table shown in FIG. 17. When the designated eventoccurs, the content defined by the event format is notified withpredetermined data for each event ID.

Attribute Table of Print Job Manager

FIG. 18 shows data (attribute table) retained by each of the print jobmanagers (control programs) 501 to 509 in DISK 315. This table showsperformances and functions of print jobs which can be handled by theprint job manager. In the table each line shows one information unit(record), and data is constituted as an aggregate of a plurality ofrecords. Each record content is the same as that of Supervisor shown inFIG. 7, and each record is constituted of attribute ID 1401, type ID1402 and value 1403. FIG. 19 is a diagram showing values of attribute ID1401 and type ID 1402 of the attribute table of FIG. 18. Type IDs otherthan type ID 203 (job table type), type ID 204 (job request table type),type ID 81 (type of inhibited attribute combination list 1), type ID 82(type of inhibited attribute combination list 2), type ID 83 (type ofinhibited attribute combination list 3), type ID 84 (type of inhibitedattribute combination list 4), and type ID 85 (type of inhibitedattribute combination list 5) are the same as those which are used inthe Supervisor attribute table of FIG. 7.

An attribute ID 601 “download method for supported data” shows a methodof transmitting document data to be printed to the apparatus. In theembodiment supported are a method 1 which comprises including thedocument data in the job; and a method 2 which comprises including areference pointer (URL: Unified Resource Locator) of the document datain the job, and reading the document data indicated by the referencepointer from the apparatus if necessary.

Attribute IDs 801 to 805 are inhibited attributes indicating limits onattributes to be set in the print job placed for the print job manager.These attributes are used to show limit items. For example, when thenumber of copy sheets exceed 100, finisher setting becomes impossible.There are five types of methods of representing the limits in theinhibited attributes. As shown in {attribute ID 1: {attribute ID 2}},the attribute ID 801 holds a plurality of pairs of lists of anotherattribute ID 2 to a certain attribute ID 1. This means that when theattribute ID 1 is being set, the setting of each attribute ID 2 cannotbe performed in a print job script.

As shown in {attribute ID 1: operator identifier: value: {attribute ID2}}, the attribute ID 802 retains a plurality of pairs of lists ofanother attribute ID 2 relative to a certain attribute ID1, operatoridentifier and value. This means that in a case where the operator shownby the operator identifier for the attribute ID 1 is applied to thevalue, when a result is true, the setting of each attribute ID 2 cannotbe performed in the print job script. The operator identifier has aone-to-one correspondence with calculation of two terms of integervalues. For example, 0 denotes “=(equal)”.

As shown in {attribute ID 1: operator identifier 1: value 1: {attributeID 2: operator identifier 2: value 2}}, the attribute ID 803 retains aplurality of pairs of lists of a set of another attribute ID2, operatoridentifier 2 and value 2 relative to a certain attribute ID1, operatoridentifier 1 and value 1. This means that in a case where the operatorshown by the operator identifier 1 for the attribute ID 1 is applied tothe value 1, when a result is true, setting cannot be performed in theprint job script in such a manner that a result of application of theoperator indicated by the operator identifier 2 for each attribute ID2to the value 2 becomes true.

As shown in {(attribute ID 1: operator identifier 1: value 1): operatoridentifier 3: (attribute ID 2: operator identifier 2: value 2):{attribute ID 3}}, the attribute ID 804 retains a plurality of pairs oflists of still another attribute ID3, relative to a certain attributeID1, operator identifier 1 and value 1 and the operator identifier 3 andanother attribute ID2, operator identifier 2 and value 2. This meansthat in a case where the result of application of the operator shown bythe operator identifier 1 for the attribute ID 1 to the value 1 and theresult of application of the operator shown by the operator identifier 2for the attribute ID 2 to the value 2 are calculated as shown by theoperator identifier 3, when a result is true, each attribute ID 3 cannotbe set in the print job script.

As shown in {(attribute ID 1: operator identifier 1 value 1): operatoridentifier 3: (attribute ID 2: operator identifier 2: value 2):{attribute ID 4: operator identifier 4: value 4}}, the attribute ID 805retains a plurality of pairs of lists of a set of still anotherattribute ID4, operator identifier 4 and value 4, relative to a certainattribute ID1, operator identifier 1 and value 1 and the operatoridentifier 3 and another attribute ID2, operator identifier 2 and value2. This means that in a case where the result of application of theoperator shown by the operator identifier 1 for the attribute ID 1 tothe value 1 and the result of application of the operator shown by theoperator identifier 2 for the attribute ID 2 to the value 2 arecalculated as shown by the operator identifier 3, when a result is true,setting cannot be performed in the print job script in such a mannerthat when calculation is performed on each attribute ID 4 andcalculation shown by 4 is applied to the value 4, a result becomes true.

The attribute ID 2001 “list of controller ID (possibly) executing Job”is a list of controller ID of the controller which executes the printjob, and the print job managers other than the print job manager 508 aresurely on a list of controllers which surely execute the job. Since theprint job manager 508 dynamically selects the controller in accordancewith the function demanded for the job, the attribute indicates acontroller selection range. The attribute ID 2002 “controller autoselection is possible or not” indicates whether the print job managerautomatically selects the controller. In the embodiment, only the printjob manager 508 sets the value to be true. The other attribute IDs arethe same as those which are used in the Supervisor attribute table ofFIG. 7. However, setting ranges and influenced ranges are limited tothose which are under control of the printer job manager to which theattribute table belongs. For example, an attribute value 101 “supportedoperation” is a list of operations which can be issued to the print jobmanager, and an attribute value 406 “charge limit data” puts a chargelimit on the print job executed by the print job manager. For treatmentin a case where the charge limit is exceeded, the service of the printjob manager is merely invalidated, and services of the other managersare not influenced. Additionally, the attribute table of the print jobmanager shown in FIG. 18 is an attribute table of service ID 4 (printjob manager 504), and attribute tables of print job managers 501, 502,503, 505, 506, 507, 508, 509 corresponding to service IDs 1, 2, 3, 5, 6,7, 8, 9, respectively are stored in DISK 315 and differ from oneanother.

Job Table

FIG. 20 is a diagram showing data (job table) retained by the print jobmanager, and shows a file name to job ID table in which a job entitymanaged by the print job manager is retained. The table is retained inRAM 302 as attribute values of attribute ID (job table) of the attributetable shown in FIG. 18. The print job manager dynamically changes thejob table on RAM 302 and stores the table in DISK 315 if necessary. Inthe table each line shows one information unit (record), and data isconstituted as an aggregate of a plurality of records. Each record isconstituted of a job ID 1501 and a file name 1502 in which the jobentity is retained. The job ID 1501 is an identifier allocated to thejob by the print job manager when the job is transmitted to the printjob manager. The job file name 1502 is a name of the file in which thejob entity is retained. As shown in FIG. 52, the job entity isconstituted of a plurality of sets of attribute ID, attribute value sizeand attribute value.

Job Request Table

FIG. 21 is a diagram showing a job request table retained by the printjob manager, and shows a relation between a job managed by the printmanager and a job executed by the controller. This table is retained inDISK 315 as attribute values of attribute ID 2004 (job request table) ofthe attribute table shown in FIG. 18. The job request table shows a typeof controller to execute a job managed by the print job manager and atype of job executed by the controller. In the table each line shows oneinformation unit, and data is constituted as an aggregate of a pluralityof records. Each record is constituted of a job ID 1503, a controller ID1504, and a job ID 1505 allocated in the controller. The job ID 1503 isan identifier allocated to the job by the print job manager when the jobis transmitted to the print job manager, and corresponds to the job ID1501 in the job table (FIG. 20). The controller ID 1504 shows ID of thecontroller by which the job is executed. The job ID 1505 is a jobidentifier allocated by the controller to execute the job.

Attribute Table of Scan Job Manager

FIG. 22 shows an attribute table which is data retained by the scan jobmanager 419. This table shows performances and functions of scan jobswhich can be treated by the scan job manager. In the table each lineshows one information unit (record), and data is constituted as anaggregate of a plurality of records. Each record content is the same asthat of Supervisor shown in FIG. 7, and is constituted of attribute ID1601, type ID 1602 and value 1603. FIG. 23 is a diagram showing valuesof attribute ID 1601 and type ID 1602 of the attribute table of FIG. 22.An attribute ID=602 “upload method for supported data” shows a method oftransmitting scanned document data to the apparatus. In the embodiment,supported are a method 1 which comprises including the document dataduring returning of the job; and a method 2 which comprises retainingthe document data in the apparatus, including a reference pointer (URL:Unified Resource Locator) to the document data during the job returning,and reading the document data indicated by the reference pointer fromhost (Client) if necessary. An attribute ID=1201 “list of supportedimage formats” shows data formats of images which can be outputted, andone of the formats can be designated as a data format during issuance ofthe scan job. A job table of attribute ID=2003 is the same as thatretained by the print job manager shown in FIG. 20. The other attributeIDs are the same as those used in the Supervisor attribute table of FIG.7. However, setting ranges and influenced ranges are limited to thosewhich are under control of the scan job manager to which the attributetable belongs. Type IDs other than the type ID 203 (job table type) ofthe attribute table of FIG. 23 are the same as those which are used inthe Supervisor attribute table of FIG. 7.

Attribute Table of Copy Job Manager

FIG. 24 shows data (attribute table) retained by each of the copy jobmanagers 601 to 608. This table shows performances and functions of copyjobs which can be treated by the copy job manager. In the table eachline shows one information unit (record), and data is constituted as anaggregate of a plurality of records. Each record content is the same asthat of Supervisor shown in FIG. 7, and is constituted of attribute ID1701, type ID 1702 and value 1703. FIG. 25 shows values of attribute ID1701 and type ID 1702 of the attribute table of FIG. 24. An attribute ID1302 (color print is possible or not), attribute ID 1303 (type ofsupported finishing), attribute ID 1304 (highest resolution that can beset), attribute ID 1305 (lowest resolution that can be set), attributeID 2001 (list of controller ID possibly executing Job), attribute ID2002 (controller auto selection is possible or not), and attribute ID2003 (job table) are the same as those which have been shown indescriptions of the print job manager and scan job manager. Moreover,attribute IDs and type IDs other than the attribute ID 1302 (color printis possible or not), attribute ID 1303 (type of supported finishing),attribute ID 1304 (highest resolution that can be set), attribute ID1305 (lowest resolution that can be set), attribute ID 2001 (list ofcontroller ID possibly executing Job), attribute ID 2002 (controllerauto selection is possible or not), attribute ID 2003 (job table), andtype ID 203 (job request table type) are the same as those which areused in the Supervisor attribute table of FIG. 7. Additionally, theattribute table of the copy job manager shown in FIG. 24 is an attributetable of service ID 18 (copy job manager 608), and the attribute tablesof the copy job managers 601 to 607 corresponding to service IDs 11 to17 are stored in DISK 315, respectively, and differ from one another.

Attribute Table of Font Manager

FIG. 26 shows data (attribute table) retained in DISK 315 by the fontmanager 413. This table shows font types which can be treated by thefont manager, a font list currently managed by the font manager, and thelike. In the table each line shows one information unit (record), anddata is constituted as an aggregate of a plurality of records. Eachrecord content is the same as that of Supervisor shown in FIG. 7, and isconstituted of attribute ID 1801, type 1802 and value 1803. FIG. 27shows values of attribute ID 1801 and type ID 1802 of the attributetable of FIG. 26. Attribute IDs and type IDs other than attribute ID 601(download method for supported data), attribute ID 602 (upload methodfor supported data), attribute ID 1501 (list of supported font types),attribute ID 1502 (Max. No. of retainable fonts), attribute ID 1503 (No.of currently retained fonts), attribute ID 1504 (list of retainedfonts), and type ID 150 (font table) are the same as those which areused in the Supervisor attribute table of FIG. 7. However, settingranges and influenced ranges are limited to those under control of thefont manager to which the attribute table belongs. The attribute ID 601“download method for supported data” and attribute ID 602 “upload methodfor supported data” are the same as those which are described indescriptions of the print job manager and scan job manager,respectively, and show methods of downloading and uploading supportedfont data.

Font Table

FIG. 28 shows a font table retained by the font manager. This table isretained in DISK 315 as attribute values of the type ID 1504 (fonttable) of the attribute table shown in FIG. 26. The font table shows atype of font which is currently managed by the font manager. In thetable each line shows one information unit (record), and data isconstituted as an aggregate of a plurality of records. Each record isconstituted of a font ID 1901, a font type 1902, a font name 1903, and afile name 1904 including font data. The font data is stored in DISK 315,and is an identifier allocated to the font by the font manager when thefont data is downloaded to RAM 302.

Attribute Table of Form Overlay Manager

FIG. 29 shows data (attribute table) retained in DISK 315 by the formoverlay manager 414. This table shows formats of form overlays which canbe treated by the form overlay manager, a list of form overlayscurrently managed by the form overlay manager, and the like. In thetable each line shows one information unit (record), and data isconstituted as an aggregate of a plurality of records. Each recordcontent is the same as that of Supervisor shown in FIG. 7, and isconstituted of attribute ID 2001, type ID 2002, and value 2003. FIG. 30shows values of the attribute ID and type ID of the attribute table ofFIG. 29. Attribute IDs and type IDs other than the attribute ID 601(download method for supported data), attribute ID 602 (upload methodfor supported data), attribute ID 1601 (list of supported form overlayformats), attribute ID 1602 (Max. No. of retainable form overlays),attribute ID 1603 (No. of currently retained form overlays), attributeID 1604 (list of retained form overlays) and type ID 160 (form table)are the same as those which are used in the Supervisor attribute tableof FIG. 7. However, setting ranges and influenced ranges are limited tothose under control of the form overlay manager to which the attributetable belongs. The attribute ID 601 “download method for supported data”and attribute ID 602 “upload method for supported data” are the same asthose which are described in descriptions of the print job manager andscan job manager, respectively, and show methods of downloading anduploading supported form overlay data.

Form Overlay Table

FIG. 31 shows a form overlay table retained by the form overlay manager414. This table is retained in DISK 315 as attribute values of attributeID 1604 (form overlay table) of the attribute table shown in FIG. 29.The form overlay table shows a type of form overlay which is currentlymanaged by the form overlay manager. In the table each line shows oneinformation unit (record), and data is constituted as an aggregate of aplurality of records. Each record is constituted of a form overlay ID2101, a form overlay data format 2102, a form overlay name 2103, and afile name 2104 including form overlay data. The form overlay data isstored in DISK 315, and the form overlay ID 2101 is an identifierallocated to the font by the form overlay manager when the form overlaydata is downloaded to RAM 302.

Attribute Table of Log Manager

FIG. 32 shows data (attribute table) retained in DISK 315 by the logmanager 415. This table shows a list of logs currently managed by thelog manager, and the like. In the table each line shows one informationunit (record), and data is constituted as an aggregate of a plurality ofrecords. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted of attribute ID 2201, type ID 2202, and value2203. FIG. 33 shows values of attribute ID and type ID of the attributetable of FIG. 32. Attribute IDs and type IDs other than the attribute ID602 (upload method for supported data), attribute ID 1703 (No. ofretained Logs), attribute ID 1704 (list of retained logs), attribute ID1705 (Log format table), type ID 170 (log table), and type ID 171 (logformat table type) are the same as those which are used in theSupervisor attribute table of FIG. 7. However, setting ranges andinfluenced ranges are limited to those under control of the log managerto which the attribute table belongs.

Log Table

FIG. 34 shows a log table retained by the log manager 415. This table isretained in DISK 315 as attribute values of the attribute ID 1704 (logtable) of the attribute table shown in FIG. 32. The log table shows atype of log currently managed by the log manager. In the table each lineshows one information unit (record), and data is constituted as anaggregate of a plurality of records. Each record is constituted of a logID 2301, and a file name 2302 including log data. The log ID 2301 is alog identifier prescribed beforehand for the type.

Contents of Log Data

FIG. 35 shows contents of log data managed by the log manager with DISK315. The log data is constituted as an aggregate of log records. Eachlog record is constituted of log format ID 2401, record date 2402 andlog data 2403. The log format ID 2401 refers to log format informationrecorded in the log format table shown in FIG. 36, and shows formats ofthe log data 2403. For example, log data “12345, 4, 1.23, “OK”” of LogFormat ID 1 means that user ID from which the job is issued to the printjob manager of service ID 1 is 12345, the number of outputted sheets is4, an amount of used toner is 1.23, and job completion state is OK.

Log Format Table

FIG. 36 shows a log format table retained by the log manager 415. Thistable is retained in DISK 315 as attribute values of the attribute ID(log format table) of the attribute table shown in FIG. 32. The logformat table shows a format of the log recorded in each log data managedby the log manager 415. In the table each line shows one informationunit (record), and data is constituted as an aggregate of a plurality ofrecords. Each record is constituted of log format ID 2501, and logformat 2502. The log format is shown as a list of a pair of service IDand attribute ID. The attribute ID is defined to be unique in theapparatus, and the type is univocally determined by the attribute ID.Therefore, by designating the attribute ID, the format of log data canbe shown. The list of the pair of service ID and attribute ID of logformat 2502, and a list of values in the log data 2403 correspond toeach other by sequence. For example, a third pair of service ID andattribute ID of the list of log format 2502 means a format of a thirdvalue of log data. For example, format “1:701, 1:565, 1:765, 1:777” ofLog Format ID 1 shows the user ID from which the job is issued to theprint job manager of service ID 1, the number of outputted sheets, theamount of used toner, and the completion state of the job. Moreover,format “11:701, 11:565, 11:765, 11:777” of Log Format ID 2 shows theuser ID from which the job is issued to the print job manager of serviceID 11, the number of outputted sheets, the amount of used toner, and thecompletion state of the job.

Attribute Table of Color Profile Manager

FIG. 37 shows data (attribute table) retained in DISK 315 by the colorprofile manager 416. This table shows formats of color profiles whichcan be treated by the color profile manager, and a list of colorprofiles currently managed by the color profile manager. In the tableeach line shows one information unit (record), and data is constitutedas an aggregate of a plurality of records. Each record content is thesame as that of Supervisor shown in FIG. 7, and is constituted ofattribute ID 2601, type ID 2602, and value 2603. FIG. 38 shows values ofattribute ID and type ID of the attribute table of FIG. 37. AttributeIDs other than attribute ID 601 (download method for supported data),attribute ID 602 (upload method for supported data), attribute ID 1801(list of formats of supported color profile data), attribute ID 1802(Max. No. of retainable color profiles), attribute ID 1803 (list ofcurrently retained color profiles), attribute ID 1804 (color profiletable), and type ID 180 (color profile table type) are the same as thosewhich are used in the Supervisor attribute table of FIG. 7. However,setting ranges and influenced ranges are limited to those under controlof the color profile manager to which the attribute table belongs. Theattribute ID 601 “download method for supported data” and attribute ID602 “upload method for supported data” are the same as those which aredescribed in descriptions of the print job manager and scan job manager,respectively, and show methods of downloading and uploading supportedfont data.

Color Profile Table

FIG. 39 shows color profiles retained by the color profile manager. Thistable is retained in DISK 315 as attribute values of attribute ID 1804(color profile table) of the attribute table shown in FIG. 37. The colorprofile table shows a type of color profile currently managed by thecolor profile manager. In the table each line shows one information unit(record), and data is constituted as an aggregate of a plurality ofrecords. Each record is constituted of a color profile ID 2701, a colorprofile format 2701 and a file name 2703 including color profile data.The color profile ID 2701 is an identifier allocated to the colorprofile by the color profile manager when the color profile data isdownloaded. The color profile data comprises data transmitted fromScanner Engine 102 and correction data for correcting data transmittedto Ink Jet Printer Engine 105 to perform color matching.

Attribute Table of Printer Controller

FIG. 40 shows data (attribute table) retained in DISK 315 by each of theprinter controllers 510, 511, 512. This table shows performances andfunctions of the print engine and finisher controlled by the printercontroller, and values concerning the performances and functions cannotbe rewritten. In the table each line shows one information unit(record), and data is constituted as an aggregate of a plurality ofrecords. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted of attribute ID 2801, type ID 2802, and value2803. FIG. 41 shows values of attribute ID and type ID of the attributetable of FIG. 40. Attribute IDs and type IDs other than attribute ID 12(controller type), attribute ID 13 (controller ID), attribute ID 5001(color print is possible or not), attribute ID 5002 (type of supportedfinishing), attribute ID 5003 (highest resolution that can be set),attribute ID 5004 (lowest resolution that can be set), attribute ID 5005(job queue table), and type ID 500 (job queue table type) are the sameas those used in the Supervisor attribute table of FIG. 7. However,setting ranges and influenced ranges are limited to those under controlof the printer controller to which the attribute table belongs.Additionally, the attribute table of the printer controller shown inFIG. 40 is an attribute table of service ID 21 (printer controller 510),and the attribute tables of the printer controllers 511, 512corresponding to service IDs 22, 23 are stored in DISK 315,respectively, and differ from each other.

Job Queue Table

FIG. 42 shows a job queue table retained by the printer controller. Thistable is retained in DISK 315 as attribute values of attribute ID 5005(job queue table) of the attribute table shown in FIG. 40. The job queuetable shows a state of the job managed and executed by the printercontroller. In the table each line shows one information unit (record),and data is constituted as an aggregate of a plurality of records. Eachrecord is constituted of a job ID 2901, a job status 2902 and a filename 2903 in which a job entity is retained. The job ID 2901 is anidentifier allocated to the job by the printer controller when the jobis transmitted to the printer controller. FIG. 43 is a diagram showingthe job status 2902 (job state) of FIG. 42: 1 denotes that the job iscompletely executed; 2 denotes that the job is being executed by theengine; and 3 denotes that the job is on standby. The job file name 2903is a name of a file in which the job entity is retained. As shown inFIG. 52, the job entity has a plurality of sets of attribute ID,attribute value size and attribute value.

Attribute Table of Scanner Controller

FIG. 44 shows data (attribute table) retained in DISK 315 by the scannercontroller 420. This table shows performances and functions of thescanner engine controlled by the scanner controller, and valuesconcerning the performances and functions cannot be rewritten. In thetable each line shows one information unit (record), and data isconstituted as an aggregate of a plurality of records. Each recordcontent is the same as that of Supervisor shown in FIG. 7, and isconstituted of attribute ID 3001, type ID 3002, and value 3003. FIG. 45shows values of the attribute ID and type ID of the attribute table ofFIG. 44. Attribute IDs other than attribute ID 12 (controller type),attribute ID 13 (controller ID), attribute ID 6001 (color scan ispossible or not), attribute ID 6002 (maximum original size), attributeID 6003 (highest resolution that can be set), and attribute ID 6004(lowest resolution that can be set) are the same as those which are usedin the Supervisor attribute table of FIG. 7. However, setting ranges andinfluenced ranges are limited to those under control of the printercontroller to which the attribute table belongs.

Structure of Command Packet

FIG. 46 shows a structure of the command packet transmitted to theinterpreter 409 from the user interface manager 405, the TCP/IP, UDP/IPprocessing module 406, the IEEE 1284.4 processing module 407 and theSBP-2 processing module 408. The command packet also shows structures ofa reply packet and an event packet transmitted to the user interfacemanager 405, the TCP/IP, UDP/IP processing module 406, the IEEE 1284.4processing module 407 and the SBP-2 processing module 408 from theinterpreter 409. The packet comprises a packet header 3101 indicating atop of the packet, a packet version 3102 indicating a packet structureversion, a flag 3103 indicating a packet property, an operation code3104 indicating a type of operation to be performed, a block number 3105used for Client (PC) to recognize the reply packet, a parameter length3106 indicating a length of parameter 3110, user ID 3107 and password3108 for use in user authentication, a status code 3109 used only in thereply packet and indicating a general reply state, and a parameter 3110having a format determined for each operation code 3105. The parameter3110 includes access target service ID, access target attribute ID, andthe like. The flag 3104 includes a flag 3111 indicating that the packetis a command packet, event packet or reply packet, and a continuous flag3112 indicating that data to be transmitted cannot be included in theparameter 3110 and continued data is also included in the packet to betransmitted next. The length of the parameter 3110 is limited to anumeral (64 k byte) indicative of the parameter length 3106.Specifically, Client PC 202 and 203 connected to Ethernet 208 designateIP address and port number to connect with the multi-function peripheral201 and output IP packet data to Network Interface 305 (107). Client PC204 connected to IEEE 1394 interface 206 designates node ID and LUN(logical unit number) to connect to the multi-function peripheral 201and output SBP-2 packet data to IEEE 1394 Interface 306 (108). Client PC205 connected to IEEE 1284 interface 207 designates the socket number toconnect to the multi-function peripheral 201 and outputs IEEE 1284.4packet data to IEEE 1284 Interface 307 (109). Via Network InterfaceDriver 402, IEEE 1284 Interface Driver 403, and IEEE 1394 InterfaceDriver 404, the command packets shown in FIG. 46 with IP Header, 1284Header, and 1394 Header added to their tops, respectively, are outputtedto the TCP/IP, UDP/IP processing module 406, the IEEE 1284.4 processingmodule 407, and the SBP-2 processing module 408. The TCP/IP, UDP/IPprocessing module 406, the IEEE 1284.4 processing module 407, and theSBP-2 processing module 408 process the received transport packets toextract the command packets shown in FIG. 46 and transmit outputs toInterpreter/Generator 409.

Processing of Command Packet

FIG. 47 shows a processing flow of the command packet in themulti-function peripheral 201. In step 3201, data transmitted from theinterfaces 401 to 404 are processed by the transport processing modules405 to 408 to extract the command packets shown in FIG. 46. Theextracted command packets, together with information of the connectiontype by which the data is entered (connection type ID) and thesubaddress, are transmitted to the interpreter 409 from the TCP/IP,UDP/IP processing module 406, the IEEE 1284.4 processing module 407, andthe SBP-2 processing module 408. In step 3202, the interpreter 409refers to the subaddress to service ID table (FIG. 9) retained bySupervisor 410, and compares the entered connection type ID andsubaddress to obtain the service ID and to check whether or not the datainput is valid. As a check result, when the data input is not valid, instep 3204 the command packet is canceled to end the flow. When the datainput is valid, in step 3203 the command packet is analyzed based on thepacket structure of FIG. 46. As a result of the packet analysis, eachitem shown in FIG. 46 is outputted as independent and separateinformation. In step 3205, by referring to the access control table(FIG. 14) based on the service ID, the security level for the service IDis obtained.

In step 3206, it is checked whether the security level obtained in thestep 3205 is 0 or 1. When the security level is 0 or 1, data istransmitted to the dispatcher 412 without checking the security level(security gate 411). In the step 3206, when the security level is otherthan 0 and 1, in step 3207 it is checked whether or not the securitylevel is 2. When the security level is 2, in step 3209 it is checkedwhether or not the user ID included in the command packet is in the userauthentication table (FIG. 13). When the user ID is not included, it isjudged that there is no authority. In step 3210 error reply informationis generated, a packet is generated by the interpreter 409 (fill thestatus code 3109 with error information), and the packet is sent to acommand packet sender. When the user ID is included, data is transmittedto the dispatcher 412. A sender address is extracted from the transportpacket (Header). In step 3207, when the security level is other than 2,in step 3208 it is checked whether the pair of user ID and passwordincluded in the command packet is present in the user authenticationtable (FIG. 13). When the pair of user ID and password is not included,it is judged that there is no authority. In step 3211 the error replyinformation is generated, the packet is generated by the interpreter409, and the packet is sent to the command packet sender. When the userID is included, data is transmitted to the dispatcher 412. In step 3212the dispatcher 412 determines a distribution addressee manager based onthe service ID, and distributes to the determined manager the connectiontype ID and subaddress to which the data is transmitted, sender address,operation code, block number, flag information, user ID, password,parameter length and parameter. Subsequently, in step 3213 each managerprocesses these information.

Access Processing of Attribute Table

FIG. 48 shows a processing when Client instructs reading or writing forthe attribute table of each manager or controller retained by themulti-function peripheral 201. The reading and writing for the attributetable retained by each manager or controller are performed bytransmitting an appropriate command packet to the subaddress ofSupervisor. In the attribute table reading command packet, asparameters, access target service ID and access target attribute ID areincluded. Moreover, in the attribute table writing command packet, asparameters, access target service ID, access target attribute ID andattribute value corresponding to the attribute ID are included. Thepacket data transmitted to the multi-function peripheral 201 from Clientis processed by the flow shown in FIG. 47, and distributed toSupervisor. In step 3301 it is checked whether or not the operation code3104 is a code for reading the attribute value (“Get”). When theoperation code is “Get”, in step 3301 based on the service ID the entireattribute table of the access target is obtained. When the service ID is0, the attribute table of Supervisor 410 shown in FIG. 7 is obtained.When the service ID is 1, 2, 3, 4, 5, 6, 7, 8, 9, the attribute table ofthe print job manager as shown in FIG. 18 is obtained. When the serviceID is 10, the attribute table of the scan job manager 419 as shown inFIG. 22 is obtained. When the service ID is 11, 12, 13, 14, 15, 16, 17,18, the attribute table of the copy job manager a shown in FIG. 24 isobtained. When the service ID is 101, the attribute table of the fontmanager 413 as shown in FIG. 26 is obtained. When the service ID is 102,the attribute table of the form overlay manager 414 as shown in FIG. 29is obtained. When the service ID is 103, the attribute table of the logmanager 415 as shown in FIG. 32 is obtained. When the service ID is 104,the attribute table of the color profile manager 416 as shown in FIG. 37is obtained. When the service ID is 21, 22, 23, the attribute table ofthe printer controller as shown in FIG. 40 is obtained. When the serviceID is 24, the attribute table of the scanner controller 420 as shown inFIG. 44 is obtained. Additionally, the attribute table of the print jobmanager shown in FIG. 18 is an attribute table of service ID 4 (printjob manager 504), and the attribute tables of print job managers 501,502, 503, 505, 506, 507, 508, 509 corresponding to service ID 1, 2, 3,5, 6, 7, 8, 9, respectively, are stored in DISK 315. In the same manner,the attribute table of the copy job manager shown in FIG. 24 is anattribute table of service ID 18 (copy job manager 608), and theattribute tables of copy job managers 601 to 607 corresponding toservice IDs 11 to 17, respectively, are stored in DISK 315. Furthermore,in the same manner, the attribute table of the printer controller shownin FIG. 40 is an attribute table of service ID 21 (printer controller510), and the attribute tables of printer controllers 511, 512corresponding to service IDs 22, 23, respectively, are stored in DISK315.

Thereafter, in step 3303, it is examined whether or not the designatedattribute value can be obtained. The examination is performed byobtaining a value of “attribute ID list available only for the manager”(attribute ID=105) of the target attribute table, and checking whetheror not the attribute ID instructed to be obtained is included. When theattribute ID is included, the value cannot be obtained. Therefore, instep 3305 the error reply packet is generated, and transmitted, therebyending the flow. When the attribute ID is not included, in step 3304 theattribute table is searched based on the designated attribute ID, andpattern ID having the corresponding attribute ID and attribute value areobtained. In step 3306, based on the pattern ID the reply packet isgenerated, and in step 3307 the reply packet is transmitted, therebyending the flow. When in step 3301 the operation code is not “Get”, instep 3308 it is checked whether or not the operation code is anattribute value writing code (“Set”). When the operation code is “Set”,in step 3309 based on the service ID an access target attribute table isentirely obtained. Thereafter, in step 3310, it is examined whether ornot the designated attribute value can be set. The examination isperformed by obtaining a value of “attribute ID list which can be setonly by the manager” (attribute ID=104) of the target attribute table,and checking whether or not the attribute ID instructed to be set isincluded. When the attribute ID is included, the value cannot beobtained. Therefore, in step 3314 the error reply packet is generated,and transmitted, thereby ending the flow. When the attribute ID is notincluded, in step 3311 based on the designated attribute ID theattribute table is searched, and the pattern ID having the correspondingattribute ID and attribute value are obtained. In step 3312, theattribute value designated based on the pattern ID is set, and the replypacket informing that the setting has succeeded is generated. In step3313 the reply packet is transmitted, thereby ending the flow. In step3308 when the operation code is not “Set”, another processing step 3315described later is performed in accordance with the operation code toend the flow.

Service ID List Inquiry Processing

FIG. 49 shows a processing when Client inquires a list of services (listof service ID) provided by the multi-function peripheral 201. Theinquiry for the service list is performed by transmitting an appropriatecommand packet to the subaddress of Supervisor, and reading andprocessing the subaddress to service ID table shown in FIG. 9. The flowshown in FIG. 49 shows details of the step 3315 (processing of otherOperation Code) of the flow shown in FIG. 48. In step 3401, it ischecked whether or not the operation code is a service list obtainingcode (“List Service”). When the operation code is not “List Service”,another processing step 3402 described later in accordance with theoperation code is performed to end the flow. In step 3401, when theoperation code is “List Service”, in step 3403, only the service IDscorresponding to the connection type ID used in the inquiry areextracted from the subaddress to service ID table to generate the list.In step 3404, each record of the list prepared in the step 3403 isexamined. When the valid flag 804 is valid, and there is a value in thevalid user list 805, the record not corresponding to the value for theuser ID used in the inquiry is deleted. When there is a value in theinvalid user list 806, the record corresponding to the value for theuser ID used in the inquiry is deleted from the list. In step 3405, thereply packet including the service ID list updated in the step 3404 isgenerated, and the generated reply packet is transmitted in step 3406.

Subaddress Inquiry Processing

FIG. 50 shows a processing when Client designates service ID to inquiresubaddress information necessary for using the service provided by themulti-function peripheral 201. The inquiry of the subaddress isperformed by transmitting an appropriate command packet to thesubaddress of Supervisor 410, and reading and processing the subaddressto service ID table shown in FIG. 9. The subaddress inquiry commandpacket includes the service ID as the parameter. The flow shown in FIG.50 shows details of the step 3402 (processing of other Operation Code)of the flow shown in FIG. 49. In step 3501, it is checked whether or notthe operation code is a subaddress obtaining code (“Reserve”). When theoperation code is not “Reserve”, other processing step 3502 describedlater in accordance with the operation code is performed to end theflow. In step 3501, when the operation code is “Reserve”, in step 3502,from the connection type ID used in the inquiry and the service IDdesignated in the parameter, the subaddress to service ID table isscanned to search for the corresponding record. For the record searchedin the step 3504, it is checked whether or not the valid flag is valid.When there is a value in the valid user list, it is checked whether ornot the user ID used in the inquiry is in the list. When there is avalue in the invalid user list, it is checked whether no user ID used inthe inquiry is in the list. As a check result, when answer is not OK, itis judged that there is no right to access (right to use) the designatedservice. In step 3506 the error reply packet is generated, and in step3507 the packet is sent, thereby ending the flow. As a result of thecheck in the step 3504, when the answer is all OK, in step 3505 thereply packet including the subaddress is generated, and in step 3507 thepacket is sent, thereby ending the flow.

Task Type Designated Service ID Inquiry Processing

FIG. 51 shows a processing flow for designating a service type andinquiring an optimum service ID to process the designated type ofservice, among the services provided by the multi-function peripheral201. The inquiry of the service ID with the designated service type isperformed by transmitting an appropriate command packet to thesubaddress of Supervisor, and reading and processing the subaddress toservice ID table shown in FIG. 9 and the service ID to task type tableshown in FIG. 11. The subaddress ID inquiry command packet includes thetask type for designating the service type, and a combination (conditioninformation) for limiting the service as parameters. The conditioninformation is shown as a list of a pair of attribute ID and value. Theflow shown in FIG. 51 shows details of the step 3503 (processing ofanother Operation Code) of the flow shown in FIG. 50. In step 3601, itis checked whether or not the operation code is a subaddress obtainingcode (“Get Service”). When the operation code is not “Get Service”,another processing step 3603 described later in accordance with theoperation code is performed to end the flow. In the step 3601 when theoperation code is “Get Service”, in step 3602 from the connection typeID used in the inquiry and the subaddress to service ID table, a serviceID list having the connection type ID used in the inquiry is generated.In step 3604, the service ID to task type table is referred to, and alist of service IDs having the designated task type is generated fromthe above-described list. In step 3605, each record of the listgenerated in the step 3604 is examined. When the valid flag 804 isvalid, and there is a value in the valid user list 805, the record notcorresponding to the value for the user ID used in the inquiry isdeleted. When there is a value in the invalid user list 806, the recordcorresponding to the value for the user ID used in the inquiry isdeleted from the list. In step 3609, the condition information includedin the parameter and the attribute table of each manager for the serviceID in the list are compared, and values other than values satisfying theconditions are deleted from the list. In step 3606, the number ofrecords of the list changed in the step 3605 is checked. When the numberof records is 0, it is judged that there is no requested service. Instep 3611 the error reply packet is generated, and in step 3613 thereply packet is sent, thereby ending the flow. In the step 3606 when thenumber of records is other than 0, in step 3607 it is checked whether ornot the number of records is 1. When the number of records is 1, in step3612 the reply packet including the obtained service ID is generated,and in step 3613 the reply packet is sent, thereby ending the flow. Inthe step 3607, when the number of records is other than 1, in step 3608,the current load state is inquired of each manager for the service ID inthe list. The managers return the number of jobs being processed as theload state, and from these the manager having a lowest load is selected.In step 3610, the reply packet including the service ID of the selectedmanager is generated, and in the step 3613 the reply packet is sent,thereby ending the flow.

Job Structure

FIG. 52 shows an inner structure of a file (job file) which retains thejob entity managed by each manager. The file name of the job file isretained in the file name 1502 of the job table (FIG. 20). The filestructure also shows an inner structure of a file retaining the jobentity managed by each controller. The file name is retained in the filename 2903 of the job queue table (FIG. 42). The job entity isconstituted of a plurality of continuous sets of attribute ID 3701,attribute value size 3702 and attribute value 3703. When the jobincludes data, as shown in 3707, 3708, 3709, a value indicating data asthe attribute ID, file name size as the attribute value size, and filename of the file retaining the document data as the attribute value areretained. The attribute includes data transmission method, data format(used PDL, and the like), event type and information such as addresseeto which event notification is sent when the event occurs, andinformation dependent on the job type such as, for the print job, thenumber of copy sheets, finishing processing designation, designation offont for use, designation of form overlay for use, and the like.

Job Script Processing in Each Manager

FIGS. 53 and 54 show a processing flow of the job script in eachmanager. The job script is constituted of a series of command packetsshown in FIG. 46, and prescribed to start with operation code “JobStart” and end with operation code “Job End”. Each packet constitutingthe job script is placed in the subaddress shown by the subaddress toservice ID table shown in FIG. 9, and distributed to each manager by thecommand packet processing flow shown in FIG. 47. The processing flowshown in FIG. 53 is a processing flow for processing the command packetdistributed to each manager to generate the job file and data file shownin FIG. 52. For the operation distributed to each manager, in step 3801it is checked whether or not the operation code is a supported operationcode. The check is performed by comparing with the value of attribute“supported operation” (attribute ID 101) retained in the attribute tableby each manager. As a result of the check, when the operation is notsupported, in step 3816 the error reply packet is generated and sent,thereby ending the flow. In the step 3801 when the operation code issupported, in step 3802 it is checked whether or not the job is beingexecuted. The check is performed by examining whether or not a jobexecution flag (flag set in step 3806) is true. As a result of theexamination, when the job execution flag is false, and the job is notexecuted, in step 3804 it is checked whether or not the operation codeis “Job Start”. As a result of the check, when the operation code is not“Job Start”, in step 3816 the error reply packet is generated and sent,thereby ending the flow.

When the answer to the step 3804 is OK, in step 3805 the job ID isallocated to add an item to the job table (FIG. 20), and a new job fileis generated. Thereafter, in step 3806 the job execution flag is set tobe true, thereby ending the command packet processing. In the check ofstep 3802, when the job execution flag is true, in step 3803 it ischecked whether the operation code is “Send”. The operation code “Send”informs the manager that the parameter includes data constituting thejob. In the step 3803 when the operation code is “Send”, in step 3807 acontinuation flag entered with the command is checked. When thecontinuation flag is true, in step 3808 a new area is added to alreadypresent data file 3713, and in 3809 the parameter is written in thearea, thereby ending the flow. In the step 3807 when the continuationflag is false, in step 3810 new data file 3713 is generated, and in step3811 the parameter is written in the data file. Thereafter, in step 3812a new area is added to the job file, and in step 3813 the attribute ID3707 indicating data, the file name size 3708 and the file name 3709 ofthe new generated file are written in the area, thereby ending the flow.In the step 3803 when the operation code is not “Send”, in step 3814 itis checked whether the operation code is “Job End”. When the operationcode is “Job End”, in step 3815 job generation processing is terminated,thereby ending the flow. The job generation terminating processingincludes processings such as closing of the job file, and the like, anddiffers with manager types (print job, scan job, copy job, font, formoverlay, log, color profile).

In the step 3814, when the operation code is not “Job End”, in step 3817it is checked whether the operation code is “Set Job”. The operationcode “Set Job” informs the manager that the parameter includes theattribute (attribute ID and attribute value) constituting the job. Whenthe job operation code is “Set Job”, in step 3818 a new area is added tothe job file, and in step 3819 the attribute ID, attribute value sizeand attribute value are written in the added area, thereby ending theflow.

In the step 3817, when the operation code is not “Set Job”, in step 3820it is checked whether the operation code is “Send Request”. Theoperation code “Send Request” instructs the manager to transmit thedata, and the data transmission method is included as the parameter.When the operation code is “Send Request”, in step 3821 a processingaccording to each manager is performed to end the flow. In theprocessing of the step 3821 for the scan job manager, the scannercontroller is instructed to scan the original in accordance with theattribute value retained in the job file, and to transmit obtained datain a designated method. For the font manager, the processing includestransmission of the font data designated as the attribute value in thejob file immediately in a designated transmission method. In the step3820 when the operation code is not “Send Request”, in step 3822 otheroperation codes are processed to end the flow.

Job Processing in Print Job Manager

FIG. 55 shows a job processing flow in the print job managers 501 to 509shown in FIG. 5. The print job manager operates a task of constantlymonitoring the job table. The print job manager performs the job scriptprocessing flow shown in FIG. 54. Subsequently, when it is detected thata new item is added to the job table by input of operation code “JobStart”, the monitor task operates a task having the processing flowshown in FIG. 55 to process the input job. In step 3901 the managerwaits until an attribute indicating a PDL (Page Description Language)type used in representation of data (document data) is added to the jobfile. When the PDL type is determined, the manager waits until PDLRasterizer for use (PDL Rasterizer 417 or 418) can be used. In the step3901 when the PDL Rasterizer becomes ready for use, in step 3902 themanager waits until the attribute indicating data reception method isadded to the job file. When the attribute indicating the data receptionmethod is added to the job file, in step 3903 the data reception methodis checked. When the data reception method comprises accessing anexternal source (e.g., Client PC on the network, and the like) of themulti-function peripheral 201, in step 3904 a task for reading thedesignated data is generated to access the external source.Subsequently, in the step 3905 the manager waits for start of the datareading. When in the step 3903 data is included in the job (in FIG. 54in data reception by operation code “Send”), in step 3906 the managerwaits for start of data reception.

When in the step 3905 or 3906 the data reading or reception is started,in step 3907 data starts to be handed to PDL Rasterizer. Subsequently,in step 3908 image data is received from PDL Rasterizer. In step 3909the printer controller to be used is determined. The determinationincludes a case where the controller is predetermined by the attributeID 2001 (list of Controller ID executing Job) of the attribute table ofthe print job managers 501 to 507 and 509, and a case where attribute ID2002 (Controller automatic selection is possible or not) of the printjob manager 508 is designated to be possible and the printer controllernecessary for print is dynamically determined by reading the print jobfile content (attribute ID and attribute value of the job file shown inFIG. 52). In this case, for example, if color printing is designated bythe attribute ID and attribute value in the job file, Ink Jet Controller512 (CID 23) is determined. When the use of Finisher is designated bythe attribute ID and attribute value, LBP Controller 510 (CID 21) isdetermined. When the printer controller is determined, in step 3910image data is handed to each printer controller and job ID is receivedfrom the printer controller. In step 3911 in the job request table (FIG.21), the job ID, printer controller ID, and job ID received from theprinter controller are recorded as separate record for each printercontroller. Subsequently, in step 3912 the print job manager waits forjob end in each printer controller. When the job end is notified fromthe printer controller, in step 3913 the corresponding record is deletedfrom the job request table. In step 3914 it is checked whether all therequested jobs of the printer controllers are finished. When the jobstill remains in the printer controller, the flow returns to the step3912 to wait for the job end in the printer controller. When in the step3914 the requested jobs in all the printer controllers are finished, instep 3915 the job record is deleted from the job table (FIG. 20). Inthis case, the event transmission processing shown in FIG. 61 isperformed. In step 3916, the job file is searched, and in step 3917 itis checked whether there is an attribute value instructing the eventtransmission concerning the job end. If not, the processing ends. Whenthe attribute value is present, in step 3918 the attribute value is readto obtain the transmission method and addressee. In step 3919 the eventtransmission packet is generated, and the event is sent to thedesignated transmission method and addressee. In step 3920, terminationprocessings such as deletion of the job and data files, and the like areperformed, thereby ending the job processing.

Job Processing in Scan Job Manager

FIG. 56 shows a job processing flow in the scan job manager 419. Afterthe handing of the job is finished, the scan job manager starts a jobprocessing. Therefore, the scan job manager starts the job processing ofFIG. 56 as the job termination processing of the step 3815 in FIG. 54.In step 4001, the job is handed to the scanner controller 420 and job IDis received. In step 4002, to the job request table (FIG. 21), the jobID, scanner controller ID, and job ID received from the scannercontroller 420 are recorded. In step 4003 the scan job manager waits forjob end from the scanner controller 420. When the job end is notifiedfrom the scanner controller 420, scanned image data is received from thescanner controller 420, and in step 4004 the job record is deleted fromthe job table (FIG. 20). In this case, the event transmission processingshown in FIG. 61 is performed. In step 4005 the job attribute data issearched for the attribute instructing the data transmission method.When in step 4006 for the data transmission method the data isinstructed to be sent as a script, in step 4008 the data is transmittedwith other attribute information as the script. Details of processingfor data transmission from the apparatus are shown in FIG. 62. When inthe step 4006 reference transmission of data is instructed, in step 4007the data is stored in the apparatus, and reference information for thedata is transmitted with the other attribute information as the script.In step 4010 the job file is searched, and in step 4011 it is checkedwhether there is an attribute value instructing the event transmissionconcerning the job end. If not, the processing ends. When the attributevalue is present, in step 4012 the attribute value is read to obtain thetransmission method and addressee. In step 4013 the event transmissionpacket is generated, and the event is sent to the designatedtransmission method and addressee. In step 4014, termination processingssuch as deletion of the job and data files, and the like are performed,thereby ending the job processing.

Job Processing in Copy Job Manager

FIG. 57 shows a job processing flow in the copy job managers 601 to 608.After the handing of the job is finished, the copy job manager starts ajob processing. Therefore, the copy job manager starts the jobprocessing of FIG. 57 as the job termination processing of the step 3815in FIG. 53. In step 4101, the job is handed to the scanner controller420 and job ID is received. In step 4102, to the job request table (FIG.21), the job ID, scanner controller ID, and job ID received from thescanner controller 420 are recorded. In step 4103 the manager waits forjob end from the scanner controller 420. When the job end is notifiedfrom the scanner controller 420, scanned image data is received from thescanner controller 420, and in step 4104 the job record is deleted fromthe job table (FIG. 20). Subsequently, in step 4105 the printercontroller to be used is determined. The determination includes a casewhere the controller is predetermined by the attribute ID 2001 (list ofController ID executing Job) of the attribute table of the copy jobmanagers 601 to 607 and 609, and a case where attribute ID 2002(Controller automatic selection is possible or not) of the copy jobmanager 608 is designated to be possible and the printer controllernecessary for print is dynamically determined by reading the job filecontent (attribute ID and attribute value of the job file shown in FIG.52). In this case, for example, if color printing is designated by theattribute ID and attribute value in the job file, Ink Jet Controller 512(CID 23) is determined. When the use of Finisher is designated by theattribute ID and attribute value, LBP Controller 510 (CID 21) isdetermined. When the printer controller is determined, in step 4106 theimage data received from the scanner controller 420 is handed to eachprinter controller and job ID is received from the printer controller.In step 4107, to the job request table (FIG. 21), the job ID, printercontroller ID, and job ID received from the printer controller arerecorded as separate record for each printer controller.

Subsequently, in step 4108 the print job manager waits for job end ineach printer controller. When the job end is notified from the printercontroller, in step 4109 the corresponding record of the finished job isdeleted from the job request table. In step 4110 it is checked whetherall the requested jobs of the printer controllers are finished. When thejob still remains in the printer controller, the flow returns to thestep 4108 to wait for the job end in the printer controller. When in thestep 4110 the requested jobs in all the printer controllers arefinished, in step 4111 the job record is deleted from the job table(FIG. 20). In this case, the event transmission processing shown in FIG.61 is performed. In step 4112, the job file is searched, and in step4113 it is checked whether there is an attribute value instructing eventtransmission concerning the job end. If not, the processing ends. Whenthe attribute value is present, in step 4114 the attribute value is readto obtain the transmission method and addressee. In step 4115 the eventtransmission packet is generated, and the event is sent to thedesignated transmission method and addressee. In step 4116, terminationprocessings such as deletion of the job and data files, and the like areperformed, thereby ending the job processing.

Job Processing Download

FIG. 58 shows a flow concerning a data download function in the jobprocessing flows in the font manager 413, form overlay manager 414, logmanager 415 and color profile manager 416. In the job for the managers,the data managed by each manager is downloaded and uploaded. Formanagement such as reference and deletion of the data managed by eachmanager, the command packet is handed to the subaddress managed bySupervisor 410 and the attribute table of each manager is accessed asshown in FIG. 48. After the handing of the job is finished, each managerstarts a job processing concerning data download. Therefore, eachmanager starts the job processing concerning the data download of FIG.58 as the job termination processing of the step 3815 in FIG. 53. Instep 4201, the job file (FIG. 52) is scanned, and it is checked whetherthere is an attribute concerning data reception method. As a result ofthe check, when the attribute concerning the data reception method isnot present, it is judged that the job file is for upload and theprocessing flow shown in FIG. 59 is already performed. In step 4208 atermination processing is performed. In the termination processing ofthe step 4208 the job file is deleted. When in the step 4201 theattribute concerning the data reception method is present, in step 4202the data reception method is checked. When the data reception method isincluded in the job (in the data reception by operation code “Send” inFIG. 53), data is already received. Therefore, in step 4205 the receiveddata is stored as a file. When in the data reception method the data ispresent outside the apparatus, in step 4203 the designated externalsource is accessed to obtain the data, and in step 4205 the obtaineddata is stored as the file. In step 4206 the file information stored inthe step 4205 is registered in the management table managed by eachmanager (the font table (FIG. 28) by the font manager 413, form overlaytable (FIG. 31) by the form overlay manager 414, log table (FIG. 34) bythe log manager 415, or color profile table (FIG. 39) by the colorprofile manager 416) by writing a new record thereto. In step 4207,termination processings such as deletion of the job and data files, andthe like are performed, thereby ending the job processing.

Job Processing Upload

FIG. 59 shows a flow concerning a data upload function in the jobprocessing flows in the font manager 413, form overlay manager 414, logmanager 415 and color profile manager 416. When operation code “SendRequest” constituting the job script is handed, each manager starts ajob processing concerning data upload. Therefore, as a processingdependent on each manager of the step 3821 in FIG. 54, each managerstarts the job processing concerning the data upload of FIG. 59. In step4301, the attributes in the job file (FIG. 52) are checked for theattribute instructing the data transmission method. When in step 4301the data transmission method instructs transmission of data as thescript (NO), in step 4303 the data designated in the job is transmittedas the script with other attribute information. The data transmissionprocessing from the apparatus is shown in detail in FIG. 62. When in thestep 4301 reference transmission of the data is instructed, referenceinformation concerning the data designated in the job is transmitted asthe script with the other attribute information.

Job Management in Manager

FIG. 60 shows a processing flow performed when Client gives an operationinstruction (job deletion) for the jobs managed by the print jobmanagers 501 to 509, scan job manager 419 and copy job managers 601 to608 in the multi-function peripheral 201. The operation for the jobmanaged by each manager is performed by transmitting an appropriatecommand packet to the subaddress of Supervisor. The job managing commandpacket includes a service ID for specifying a target job manager, and atarget job ID as parameters. The command packet transmitted to themulti-function peripheral 201 from Client is processed by the flow shownin FIG. 47, and distributed to Supervisor 410. The processing flow shownin FIG. 60 shows details of the step 3603 (processing of other OperationCode) in the flow shown in FIG. 51. In step 4401, Supervisor 410 checkswhether the operation code is for deleting the job (“Cancel Job”). Whenthe operation code is not “Cancel Job”, another processing step 4409described later in accordance with the operation code is performed toend the flow. When in the step 4401 the operation code is “Cancel Job”,in step 4402, in accordance with the service ID designated in theparameter, the parameter is transmitted to each manager corresponding tothe service ID. In step 4403, each manager searches the job requesttable managed by each manager for a designated job ID. When in step 4404the job request table has no designated job ID, it is judged that thejob in the controller is already finished. In step 4410 thecorresponding record is deleted from the job table, and in step 4411 thereply packet is generated and sent, thereby ending the flow. When in thestep 4404 the designated job ID is present in the job request table, instep 4405 a controller job ID corresponding to the designated job ID andcontroller ID of the controller executing the job are obtained. In step4406 the job ID of the controller corresponding to the controller ID isdesignated to instruct the controller to delete the job. In step 4407,the manager waits for an execution result from the controller. When theexecution result is unsuccessful, in step 4409 the error reply packet isgenerated and sent, thereby ending the flow. When in the step 4407, theexecution result from the controller is successful, in step 4408 thecorresponding record is deleted from the job request table, and in step4403 the job request table is searched to again check whether a requestfor another controller is made.

Event Transmission

FIG. 61 shows a processing flow of event transmission in each manager.Each manager has the event setting table as shown in FIG. 16 as thevalue of the attribute table retained by itself. As shown in thedescription of FIG. 16, in the table listed are the connection type andaddressee to which the event is transmitted when the event occurs arewritten. When a certain event occurs, each manager recognizes the eventID for the event. Subsequently, in step 4501, the event setting table issearched to confirm whether the event ID is registered. When in the step4502 no event ID is registered, the processing is ended. When in thestep 4502 even one event ID is registered, in step 4503 the connectiontype for use in the event transmission and the addressee to which theevent is transmitted are obtained from the first record, and in step4504 the event transmission packet is generated. Added to the packet arethe parameter prescribed for each event ID and the parameter accordingto the format of each event ID registered in the event format table(FIG. 17) retained by Supervisor 410. In step 4505, the eventtransmission packet is transmitted to the transmission addressee of theconnection type obtained in the step 4503. Subsequently, in step 4506 itis judged whether or not all records having event IDs are completed byrepeating the steps 4503 to 4505. If not, the flow returns to the step4503. When all the records are processed, the processing is ended.

Data Script Transmission from Multi-Function Peripheral

FIG. 62 shows a processing flow when data is transmitted as a script ofcontinuous command packet from the multi-function peripheral 201. Theprocessing flow is used in the step 4008 of transmitting the image dataobtained as the result of the scan job, the step 4303 of transmittingthe font data, and the like. In step 4601, a packet including a dataattribute is generated and sent. If necessary, the step 4501 is repeatedto send a plurality of attributes. In step 4602, designated data fortransmission is obtained. Since the command packet has a structure shownin FIG. 46 and the size which can be transmitted as the parameter islimited, in 4603 a data length is examined. As a result of examination,when the data length exceeds a limit length (64 Kbyte), in step 4606 thedata is cut to the limit value of length, and in step 4607 the commandpacket with the obtained data added thereto as the parameter isgenerated and sent. In the command packet, operation code “Send” is set,and the continuation flag is set to be true. In step 4608 the rest ofthe cut data is obtained, and in the step 4603 the data length is againexamined. As a result of the examination of the step 4603, when the datalength is within limits of the command packet, in step 4604 the commandpacket with the data added thereto as the parameter is generated andsent. In the command packet, operation code “Send” is set, and thecontinuation flag is set to be false. In step 4605 a command packetincluding remaining attributes is generated and sent. If necessary, thestep 4501 is repeated, and a plurality of attributes are sent, therebyending the flow.

Hard Configuration of Client PC

FIG. 63 is a diagram showing a common hardware configuration(controller) of Client PC 202 to 205 of the embodiment shown in FIG. 2.Inside the controller, CPU 6001 is connected via a bus 6010 to Memory(RAM) 6002, a display 6003 such as CRT, a pointing device 6004 such as akeyboard, a mouse, and the like, ROM 6008, and DISK 6009. Variousprograms and data shown in FIG. 77 are stored in DISK 6009 (storagemedium) such as a hard disk, a floppy disk, and the like, aresequentially read into Memory (RAM) 6002 if necessary, and executed byCPU 6001. The DISK 6002 may be detachably attached to Client PC orincorporated in Client PC. Furthermore, the program shown in FIG. 77 maybe configured to be downloaded from other Client PC or MFP 201 via thenetwork interface cable 208 (10BASE-T), IEEE 1394 interface cable 206,and IEEE 1284 interface cable 207 and stored in DISK 6009. The hardwareshown in FIG. 63 constitutes general Client PC shown in FIG. 78. WhenCPU 6001 writes data to the display 6003, display is performed. When CPU6001 reads data from the pointing device 6004, the instruction from theuser is entered.

Moreover, to the bus 6010 a network interface connector 6005, IEEE 1394interface connector 6006, and IEEE 1284 interface connector 6007 areconnected. Then, Ethernet (10 BASE-T) cable 20w, IEEE 1394 cable 206,and IEEE 1284 cable 207 shown in FIG. 2 are connected. When CPU 6001reads or writes data via these interfaces, communication is performedusing the interfaces.

Software Configuration of Client PC

FIG. 64 shows a part of a block diagram of software (control program) ofClient PCs 202 to 205 using the multi-function peripheral 201. Thesoftware (control program) and data used by Client PC are stored in DISK6009 as shown in FIG. 77. Via a user interface 501, drivers andutilities 505 to 514 display information of the multi-functionperipheral 201 on the display 6003. A database 502 (DISK 6009) retainsinformation (data) of the currently operated multi-function peripheral201. When Client connects to the multi-function peripheral 201, anapparatus information obtainer 503 obtains all information of theapparatus and retains the information in the database 502. A prescribedinformation database 504 (DISK 6009) retains meanings of attributes,data pattern for each attribute ID, parameter format prescribed for eachevent ID, meanings of task types, Supervisor subaddress, and otherprescribed information which are used in each attribute table retainedby the multi-function peripheral 201. The drivers and utilities 505 to514 are operated based on the prescribed information database 504 andthe apparatus information database 502. A printer driver 505 generates aprint job script by an instruction from application program operating onClient PC. A scanner driver 506 generates a scan job script by aninstruction from the application program operating on Client PC. A copydriver 507 generates a copy job script by an instruction from theapplication program operating on Client PC. A font management utility508 generates a job for downloading and uploading font data, andgenerates a command for managing the font data. A form overlaymanagement utility 509 generates a job for downloading and uploadingform overlay data, and generates a command for managing the form overlaydata. A log management utility 510 generates a job for downloading anduploading log data, and generates a command for managing the log data. Acolor profile management utility 511 generates a job for downloading anduploading color profile data, and generates a command for managing thecolor profile data. A job management utility 512 generates a command forperforming management such as deleting, temporary stopping, andre-executing of the print job, scan job and copy job. An apparatusmanagement utility 513 generate a command for obtaining states of theprinter controller and scanner controller. A charge management utility514 generates a command for obtaining charge data.

A generator 515 generates a command packet based on commands generatedby the drivers and utilities 505 to 514. The generated command packet istransmitted to the multi-function peripheral 201 using transportprocessing modules 517, 519, 521. The generator 515 interprets replypackets and event packets transmitted from the transport processingmodules 517, 519, 521, and distributes the packets to appropriatedrivers or utilities. An SBP-2 processing module 517 is a transportlayer of IEEE 1394. Numeral 519 denotes a TCP/IP, UDP/IP processingmodule. An IEEE 1284.4 processing module 521 is a transport layer ofIEEE 1284. An interface 518 processes an IEEE 1394 physical layer.Numeral 520 denotes a network interface. An interface 522 processes anIEEE 1284 physical layer. FIG. 64 also shows an inner configuration ofthe user interface manager 405 in the software (control program) blockdiagram (FIG. 4) of the multi-function peripheral 201. In the userinterface manager 405, the SBP-2 processing module 517, TCP/IP, UDP/IPprocessing module 519, IEEE 1284.4 processing module 521, networkinterface 518, network interface 520, and IEEE 1284 interface 522 inFIG. 64 are not disposed, and the generator 515 is directly connected tothe interpreter 409 in FIG. 4, whereby the command packet, reply packetand event packet are exchanged. The direct connection is not present inthe software (control program) configurations of other Client PCs 202 to205.

Packet Generation/Transmission Processing

FIG. 65 shows a processing flow in which the generator 515 receives thecommands or the job scripts from the drivers and utilities 505 to 514,generates the command packet shown in FIG. 46 and transmits the packetto the multi-function peripheral 201. Before the processing flow, anappropriate subaddress of a multi-function peripheral of a transmissionaddressee is connected beforehand. Information concerning the subaddressto be connected is obtained by a flow for obtaining apparatusinformation shown in FIG. 66. The job script is defined by a continuouscommand. When a processing target is a job script, steps 4701 to 4706are repeated until all commands are processed. In the followingdescription, the issuance of the job script means that the steps 4701 to4707 are processed for each command. In step 4701, a length of data tobe transmitted with the command is examined. As a result of examination,when a parameter limit value of length (64 Kbyte) is exceeded, in step4702 the data is cut to the limit value of length. For the cut data, instep 4703 a continuation flag is set to be true and a packet includingan operation code corresponding to the command is generated, and in step4704 the packet is sent. When in the step 4701 the data length is withinparameter limits of the length, in step 4705 the continuation flag isset to be false and a packet including the operation code correspondingto the command is generated, and in step 4706 the packet is sent.

Information Obtaining in Client and Software Automatic Configuration

FIG. 66 shows a processing flowchart of the apparatus informationobtainer 503 of FIG. 64. Immediately after Client connects to themulti-function peripheral 201, the apparatus information obtainer 503performs a processing shown in FIG. 66 to obtain the apparatusinformation and retain the information in the apparatus informationdatabase 502 (DISK 6009). This processing is also performed again whenan event for changing the configuration is transmitted from theapparatus. In step 4801, Client PC connects to the multi-functionperipheral 201. Specifically, Client PCs 202 and 203 connected toEthernet 208 designate IP address and port number to connect to themulti-function peripheral 201 and output IP packet data. Client PC 204connected to IEEE 1394 interface 206 designates node ID and LUN (logicalunit number) to connect to the multi-function peripheral 201 and outputsSBP-2 packet data. Client PC 205 connected to IEEE 1284 interface 207designates the socket number to connect to the multi-function peripheral201 and outputs IEEE 1284.4 packet data. For the subaddress of theconnection addressee, the subaddress for Supervisor prescribedbeforehand for each connection type used in connection is used. Theprescribed value is obtained from the prescribed information database504 (DISK 6009). In step 4802, a value of attribute ID 100 (list ofattribute ID) of Supervisor attribute table shown in FIG. 7 is obtained.The attribute value is obtained by generating an attribute valueobtaining command (Get) by the use of Supervisor service ID andattribute ID as parameters, and transmitting the command to thegenerator 515. The generator 515 performs the processing flow of FIG.65, and transmits the command packet for obtaining the attribute valueto the multi-function peripheral 201. The multi-function peripheral 201receives the command packet, and returns to Client the attribute valueof the attribute ID designated by performing the processing flow ofFIGS. 47 and 48. Client analyzes the reply packet by the generator, andtransmits the packet to the apparatus information obtainer.Additionally, the attribute of attribute ID 100 is a list of allattribute IDs in the Supervisor attribute table. In step 4803 theattribute ID is designated to obtain the attribute value, the processingis repeated until the attribute values of all the attribute IDs areobtained in step 4804, and the attribute values are stored together withthe attribute IDs in the apparatus information database 502. In theabove steps the attribute tables (FIG. 7) of Supervisor are all storedin the apparatus information database 502.

Subsequently, in step 4805 a service ID list (the SID to TASK TYPE tableshown in FIG. 11) is obtained from the attribute table stored in theapparatus information database 502 (DISK 6009). Additionally, theservice ID may also be obtained by generating a service ID list inquirycommand (LIST SERVICE), and transmitting the command to the generator515. In this case, the multi-function peripheral 201 executes theprocessing flow shown in FIGS. 47 to 49. In steps 4806 to 4811, eachmanager information is obtained for each service ID obtained in the step4805. In step 4806 from the list shown in FIG. 11, a service ID 1 (printjob manager 501) as a first service ID of service IDs except Supervisor(service ID 0) is obtained. In step 4807 the subaddress corresponding tothe service ID is obtained. The subaddress is obtained by generating acommand (Reserve) for obtaining the subaddress using the service ID asthe parameter, and handing the command to the generator 515. In thiscase, in the multi-function peripheral 201, the processing flow shown inFIGS. 47 to 50 is executed. The obtained subaddress is stored in theapparatus information database 502. In step 4808, the value of attributeID 100 (list of attribute ID) of each manager attribute table isobtained. The attribute value is obtained by designating service ID andattribute ID for each manager as the parameters, generating a command(Get) for obtaining the attribute value, and transmitting the command tothe generator 515. In step 4809 the attribute ID is designated to obtainthe attribute value, in step 4810 processing is repeatedly performeduntil the attribute values of all attribute IDs are obtained, and theattribute values are stored with the attribute IDs in the apparatusinformation database 502. In step 4811 it is judged whether or not theservice ID is a final service ID in the list. When the service ID is notfinal, in step 4812 the next service ID is obtained from the list andthe processing is repeated from the step 4807. In step 4811 theattribute values of all the service IDs (print job managers 501 to 509,scan job manager 419, copy managers 601 to 608, font manager 413, formoverlay manager 414, log manager 415, color profile manager 416, printercontrollers 510 to 512, scanner controller 420) of the service ID listare stored with the attribute IDs in the apparatus information database502.

Subsequently, in step 4813, based on the apparatus information (data)stored in the apparatus information database 502 (DISK 6009), userinterfaces are automatically formed for managers corresponding to thedrivers and utilities (control program) 505 to 514. The processing ofthe automatic forming step 4813 includes updating of the user interface,and display of set screen (user interface) is changed in accordance withthe drivers and utilities. For example, as shown in FIGS. 81 and 82showing display screens on the display 6003, the printer driver userinterface changes displays of supported PDL list based on the attributevalue of attribute ID 1101 of each print job manager (501 to 509),availability of color printing based on attribute ID 1102, supportedFinishing type based on the attribute value of attribute ID 1103,settable highest resolution based on the attribute value of attribute ID1104, and settable lowest resolution based on attribute ID 1105.

Likewise, displays of the user interface for the other drivers 506, 507,utilities 508 to 514 are changed in accordance with the attributes.Furthermore, icons of the drivers and utilities (print manager, copy jobmanager, and the like) are displayed in such a manner that they can bedistinguished.

Moreover, the user interface may be graphical as shown in FIG. 83. In ascreen of FIG. 83, a list of the print job managers, scan job manager,and copy manager included in the service ID list (service ID listobtained in the step 4806) is displayed. Additionally, the print jobmanagers, scan job manager, and copy job manager are provided withmanager titles, and a list of the manger titles are displayed.

When the user wants to perform printing, copying or scanning of printedmatters, the user opens the screen of FIG. 83 via a device controlapplication or a device control driver. Then, from a plurality ofmanagers present in the device, the user selects the print manager toperform the printing, or selects the scan manager to perform thescanning.

Additionally, for example, the print type, sheet size, availability ofcolor printing, availability of double sided printing, possibleenlarged/reduced range, and the like of the print manager are displayedbased on the attribute values obtained in the step 4809. Here, for theprint type, the print controller to be used is determined from theattribute value of attribute ID 2001 (list of Controller ID executingjob) of the print job manager. Moreover, the availability of colorprinting is determined from the attribute value of attribute ID 1102 ofthe print job manager. Other conditions are also obtained from attributevalues of attribute IDs not shown in FIG. 19. Therefore, furtherdetailed information can also be displayed based on the attributevalues. The same is applied to the scan job manager and the copymanager.

During the job issuance, the user uses the pointing device 6004 toselect a desired manager from the manager list. Alternatively, when acheck is put in a check box of “Auto Selection of Manager” of the screenof FIG. 83, an optimum manager is automatically selected from managerfunctions and situations.

Moreover, as shown in FIG. 84, in the print screen of the applicationprogram, printer names for the print job managers may be displayed. Theprint screen is displayed when the user gives a print instruction withthe application program. Client generates virtual printers for the printjob managers based on the apparatus information of the apparatusinformation database 502 to display the printers in such a manner thatthe user can make a selection from them. For example, in the screen,“PRINTER A” indicates the print job manager 501, and “PRINTER B”indicates the print job manager 502.

Furthermore, when the user selects a certain printer name from thescreen of FIG. 83 or 84, and opens “property” screen, a screen isdisplayed as shown in FIG. 85. The user gives a further detailedprinting instruction in this screen. In this case, a sheet size,magnification, sheet feed method, and other conditions which can beselected by the user with the printer are determined based on theattribute values obtained in the step 4809 of FIG. 66.

Finally, in step 4814, Supervisor 410 is disconnected, and theprocessing is ended.

Job Issuance with Designated Task Type

FIG. 67 shows a processing when each application or utility issues a jobscript with a designated task type. The job with a designated service IDis issued by searching the apparatus information database 502 using theservice ID as a key, and transmitting an appropriate job script to theobtained subaddress. When only the task type is designated by aninstruction from the user, however, a request for introduction ofservice ID to be used needs to be made for the multi-function peripheral201. FIG. 67 shows a processing for this case. In step 4901, the tasktype is designated, an attribute value obtaining command is generated toobtain the service ID, and the command is transmitted to the generator515. In the multi-function peripheral 201 the processing flow shown inFIGS. 47 to 51 is executed. In step 4902, based on the service IDobtained in the step 4901 the apparatus information database 502 issearched, and the job script is transmitted to the obtained subaddress.

Event Structure

FIG. 68 shows a structure of the event transmitted to Client from themulti-function peripheral 201. The event packet has the same structureas that of the command packet shown in FIG. 46. FIG. 68 shows astructure of the packet parameter 3110. Numeral 5001 denotes an event IDindicating an event type, and 5002 denotes parameter data prescribed foreach event ID. A format of the data is retained beforehand in theprescribed information database 504. Numeral 5003 denotes parameter datawhose format is determined for each event ID in the apparatus. The dataformat is retained as the event format table (FIG. 17) in the apparatusinformation database 502 by executing the processing flow of FIG. 66.

Event Processing

FIG. 69 shows a processing flow when each driver or utility of Clientreceives the event from the multi-function peripheral 201. Each driveror utility registers a desired event beforehand in the generator 515using the event ID as a key. When the event is transmitted to Clientfrom the multi-function peripheral 201, the generator 515 distributesthe event to each registered driver or utility. FIG. 69 shows theprocessing after the event is distributed to each driver or utility. Instep 5101, based on the format information obtained from the prescribedinformation database 504 the prescribed parameter data 5002 is analyzed.In step 5102, using the event ID (5001) as the key, the event format1302 for the event ID is obtained from the event format table (FIG. 17)retained in the apparatus information database 502. In step 5103, basedon the obtained event format, the event format dependent on theapparatus (event format attribute ID 676: sheet size, ID 756: papertype, ID 666: toner type, ID 698: ink type, ID 600: cover position) isanalyzed. Subsequently, in step 5104 the analyzed parameter and event ID(event ID 200: no paper, ID 399: no toner, ID 432: no ink, ID 234:multi-function peripheral cover opened) are processed and displayed forthe event (e.g., no paper, cover open, no toner, and other userinterfaces are displayed on the display 6003.

Log Processing

FIG. 70 shows a flow in which the log management utility 510 obtains andprocesses the log retained by the multi-function peripheral 201. In step5201, log data is obtained. The log data is obtained by generating a jobscript for obtaining the log data, and sending the script to themulti-function peripheral 201. In the multi-function peripheral 201, theprocessing flow shown in FIGS. 47, 53, 59 is executed, and the log datais sent to Client. For example, log data “12345, 4, 1.23, “OK”” of LogFormat ID 1, 98/1/31:23 shown in FIG. 35 means that the user ID fromwhich the job is issued to the print job manager of service ID 1 is12345, the number of outputted sheets is 4, the amount of used toner is1.23, and the job completion state is OK. In step 5202, the log formattable (FIG. 36) is obtained from the apparatus information database 502.In step 5203, log format ID 2401 on the top of each record of the logdata is obtained, and from the value the log format 2502 is obtainedfrom the log format table (FIG. 36). For example, format “1:701, 1:565,1:765, 1:777” of Log Format ID 1 indicates the user ID from which thejob is issued to the print job manager of service ID 1, the number ofoutputted sheets, the amount of used toner, and the job completionstate. Moreover, format “11:701, 11:565, 11:765, 11:777” of Log FormatID 2 indicates the user ID from which the job is issued to the print jobmanager of service ID 11, the number of outputted sheets, the amount ofused toner, and the job completion state. In step 5204, the log data2403 is analyzed in accordance with the log format 2502, and theanalyzed data is processed (log sorting, and the like) with logoccurrence time 2402. Subsequently, in step 5205 it is judged whether ornot each record log data is analyzed. When the data is not analyzed, theprocessing from the step 5203 is repeatedly executed. When all the datais analyzed, the processing is ended.

Obtaining and Processing of Charge Information

FIG. 71 shows a flow in which the charge management utility 514 obtainsand processes charge data retained in the multi-function peripheral 201.The charge data is shown as count data retained by each manager. Thecount data is retained as values of attribute ID 401 in the attributetable (FIGS. 7, 18, 22, 24, 26, 29, 32, 27, 40, 44), and the valuesconstitute a list of integer values. Integer value meanings are shown asvalues of the attribute (attribute ID 402) of the count data format inthe attribute table of each manager, and the values constitute a list ofattribute ID. The count data list and the count data format listcorrespond to each other by sequence in each list. For example, thethird value of the count data means the information of the thirdattribute ID of the count data format. FIG. 71 shows the flow forobtaining and processing the count data retained by each manager. Instep 5301, a target manager service ID is designated, and the values ofattribute ID 401 (count data values) are obtained. For example, thevalue of attribute ID 401 (45, 78, 34, 13) shows the number of printsheets with a sheet size represented by the count data format of theattribute ID 402. The value of the attribute ID 401 is obtained by usingthe service ID and attribute ID as parameters, generating the commandfor obtaining the attribute value, and transmitting the command to thegenerator 515. In step 5302, the same service ID is designated, and thevalue of the attribute ID 402 (count data format value) is obtained. Forexample, attribute value 565 of the attribute ID 402 means the number ofprinted sheets with a sheet size A2, attribute value 537 means thenumber of printed sheets with a sheet size A3, attribute value 545 meansthe number of printed sheets with a sheet size A4, and attribute value523 means the number of printed sheets with a sheet size A5. The valuemay be obtained from the apparatus information database 502. In step5303, the obtained count data format is used to analyze the count data.In step 5304, the analyzed count data is used to process and generatecharge data, for example, for each service ID, each user ID, and eachdivision, thereby ending the flow.

Issuance of Print Job, Data Download Job

FIG. 72 shows processings for issuing a print job by the printer driver505, a font data download job script by the font management utility 508,a form overlay data download job script by the form overlay utility 509,a log data download job script by the log management utility 510, and acolor profile data download job script by the color profile managementutility 511. The processing flow by each software (control program) asdescribed above is common. Print target document data and theabove-described types of download target data (font data, form data,color profile data, log data) are referred to as “data” in FIG. 72 andthe following description. During the job issuance, the data to beprinted or to be downloaded are designated with a plurality of attributevalues set in the job script. In step 5401, the apparatus informationdatabase 502 is accessed to obtain apparatus information.

Subsequently, based on the obtained apparatus information, the userinterface of FIG. 83 or 84 is displayed. The user uses the pointingdevice 6004 to select the manager as a data transmission target from themanager titles listed/displayed in FIG. 83, or from the printer namesdisplayed in FIG. 84.

In step 5402, referring to the attribute table of each manager (e.g.,the print manager to designate printing for the print target documentdata) as the data transmission target, it is checked whether thedesignated attribute value is within a range of the attribute values setin the attribute table. As a result of the check, when even one value isnot in the range, in step 5405 a processing to reject the job issuanceis performed such as displaying of an error dialog on the userinterface, thereby ending the flow.

As a result of the check of step 5402, when all the attributes arewithin the range of the attribute values in the attribute table of themanager, in step 5403 it is checked whether there is an inhibitedattribute (attribute ID 801 to 805) in the manager attribute table. Whenthe manager attribute table has the inhibited attribute, in step 5404 itis checked whether the job attribute designated for each inhibitedattribute of the manager attribute table is a combination of inhibitedvalues. As a check result, when there is a combination of inhibitedattribute values, in step 5405 the processing to reject the job issuanceis performed to end the flow. When as a result of the check of step 5403the manager has no inhibited attribute, and when as a result of thecheck of step 5404 the job attribute is not a combination of inhibitedvalues, in step 5406 a data location is checked. The data location isdesignated by designating an address by the user or by generating theaddress by the application. When the data is inside Client issuing thejob, in step 5407, attribute value 601 (supported data download method)of the relevant manager attribute table in the apparatus informationdatabase 502 is checked. When in the check of step 5407 the method ofincluding data in the job is supported, in step 5408 a job scriptincluding the data in the job is generated, the packet generatingprocessing shown in FIG. 65 is performed, and the packet is transmittedto the multi-function peripheral 201. When in the check of step 5407,the method of including the data in the job is not supported, in step5409 a job script including the reference pointer (URL: Unified ResourceLocator) of the data in the apparatus into the job is generated andtransmitted. When in the check of step 5406 the data is present outsideClient issuing the job, in step 5410 attribute value 601 (supported datadownload method) of each relevant manager attribute table in theapparatus information data is checked. When in the check of step 5410 amethod of including the reference pointer in the job and reading data bythe apparatus itself is supported, a job script including the referencepointer to the data into the job is generated and transmitted. When inthe check of step 5410 the method of including the reference pointer inthe job and reading the data by the apparatus itself is not supported,in step 5412 the data is once read into the apparatus from the outside.Subsequently, in step 5413 a job script including the read data in thejob is generated and transmitted. Each manager of the multi-functionperipheral 201, which has received the job script, performs theprocessing shown in FIGS. 53, 54, 55 (print job manager) or in FIGS. 53,54, 58 (font manager, form overlay manager, log manager, color profilemanager), and processes the instructed job.

Issuance of Scan Job, Data Upload Job

FIG. 73 shows processings for issuing a scan job by the scanner driver506, a font data upload job script by the font management utility 508, aform overlay data upload job script by the form overlay utility 509, alog data upload job script by the log management utility 510, and acolor profile data upload job script by the color profile managementutility 511. The processing flow of each software (control program)described above is common. Document data obtained as a scanning resultand the above-described types of upload target data (font data, formdata, color profile data, log data) are referred to as “data” in FIG. 73and the following description. During the job issuance, an indicator toindicate the data is designated with a plurality of attribute values setin the job script. In step 5501, the apparatus information database 502is accessed to obtain apparatus information. In step 5502, referring tothe attribute table of each manager (e.g., for font data, the fontmanager to manage the font data) designating data as the upload target,it is checked whether the designated attribute value is within a rangeof the attribute values set in the attribute table. For the managerdesignating the data as the upload target, for example, for the scan jobmanager, the user selects the manager on the user interface as shown inFIG. 83.

As a result of the check, when even one value is not in the range, instep 5505 a processing to reject the job issuance is performed such asdisplaying of an error dialog on the user interface, thereby ending theflow. As a result of the check of step 5502, when all the attributes arewithin the range of the attribute values in the attribute table of themanager, in step 5503 it is checked whether there is an inhibitedattribute (attribute IDs 801 to 805) in the manager attributes. When themanager attribute table has the inhibited attribute, in step 5504 it ischecked whether the job attribute designated for each inhibitedattribute of the manager attribute table is a combination of inhibitedvalues. As a check result, when there is a combination of inhibitedattribute values, in step 5505 the processing to reject the job issuanceis performed to end the flow.

When as a result of the check of step 5503 the manager has no inhibitedattribute, and when as a result of the check of step 5504 the jobattribute is not a combination of inhibited values, in step 5506 datatransmission addressee (storage position) is checked. When the datatransmission addressee is outside the apparatus, in step 5507, the datatransmission addressee is again checked. When the data transmissionaddressee is Client issuing the job, in step 5508 attribute value 602(supported data upload method) of the relevant manager attribute tablein the apparatus information data is checked. When as a result of thecheck of step 5508 data transmission is supported, in step 5509 a jobscript instructing data transmission is issued, and in step 5510 datareception is performed. When as a result of the check of step 5508, thedata transmission is not supported (NO), in step 5511 is issued a jobscript instructing reference transmission which means that data istransmitted to the apparatus using a reference pointer to retained dataas a reply. Using information of the returned reference pointer, in step5512 data is obtained. When in step 5507 the data transmission addresseeis other than Client issuing the job, in step 5513 attribute value 602(supported data upload method) of each relevant manager attribute tablein the apparatus information data is checked. When as a result of thecheck of step 5513 the reference transmission is supported, in step 5514a job script instructing the reference transmission by the use of thetransmission addressee as the parameter is issued. In step 5515 byinforming the data transmission addressee that data is transmitted fromthe multi-function peripheral 201, an instruction for obtaining the datais transmitted. When as a result of the check of step 5513 the referencetransmission is not supported, in step 5516 a job script instructing thedata transmission is issued. In step 5517 data is received, and the datais again transmitted to the transmission addressee. When as a result ofthe check of the step 5506 the transmission addressee is inside theapparatus, in step 5518 attribute value 602 (supported data uploadmethod) of each relevant manager attribute table in the apparatusinformation data is checked. When as a result of the check of step 5518the reference transmission is supported, in step 5519 a job scriptinstructing the reference transmission by the use of the addresseeinside the apparatus as the parameter is issued. When as a result of thecheck of step 5518 the reference transmission is not supported, in step5520 a job script instructing the data transmission is issued. After instep 5521 Client receives the data, the data is again returned to theapparatus. Each manager of the multi-function peripheral 201, which hasreceived the job script, performs the processing shown in FIGS. 53, 54,56 (scan job manager) or in FIGS. 53, 54, 59 (font manager, form overlaymanager, log manager, color profile manager), and processes theinstructed job.

Issuance of Copy Job

FIG. 74 shows a processing for issuing a copy job. As an instruction ofthe copy job issuance, a plurality of attribute values to be set in thejob script are designated. In step 5601, the apparatus informationdatabase 502 is accessed to obtain apparatus information. In step 5602,the attribute table of the copy manager is referred to, and it ischecked whether the designated attribute values are within a range ofattribute values set in the attribute table. The copy manager isselected in the user interface as shown in FIG. 83 by the user.

As a result of the check, when even one value is not in the range, instep 5605 a processing to reject the job issuance is performed such asdisplaying of an error dialog on the user interface, thereby ending theflow. As a result of the check of step 5602, when all the attributes arewithin the range of the attribute values in the attribute table of thecopy manager, in step 5603 it is checked whether there is an inhibitedattribute (attribute IDs 801 to 805) in the copy manager attributetable. When the copy manager attribute table has the inhibitedattribute, in step 5604 it is checked whether the job attributedesignated for each inhibited attribute in the attribute table of thecopy manager is a combination of inhibited values. As a check result,when there is a combination of inhibited attribute values, in step 5605the processing to reject the job issuance is performed to end the flow.When as a result of the check of step 5603 the manager has no inhibitedattribute, and when as a result of the check of step 5604 the jobattribute is not a combination of inhibited values, in step 5606 the jobscript is generated and issued, thereby ending the flow. The copy jobmanager of the multi-function peripheral 201 which has received the jobscript performs the processing shown in FIGS. 53, 54, 57, and managesthe instructed job.

Issuance of Job Management Command

FIG. 53 is a processing flow when the job management utility 512 issuesa job management command. In step 5701 the service ID of the targetmanager is used as the parameter to obtain the job table (FIG. 20)retained by the manager from MFP 201. In step 5702, the job ID owned bythe management target job is selected from the job list included in theobtained job table in an appropriate method. Selecting means includes amethod which comprises displaying the job list on the display 6003 viathe user interface 501 so that the user selects the job ID, and othermethods. In step 5703 the designated job ID is used as the parameter togenerate the command for managing the job, and the command is issued,thereby ending the flow. Supervisor of the multi-function peripheral 201which has received the job management command performs the processingshown in FIGS. 47 to 51 and 60, and manages the instructed job.

Additionally, the present invention may be applied to a systemconstituted of a copying machine, a printer, a scanner, and other singleunits, or may be applied to a device constituted of one apparatus (e.g.,a copying machine, a facsimile device, and the like). Moreover, theobject of the present invention is attained by providing the system withthe storage medium (FIGS. 76, 77) in which the program code of software(control program) for realizing the above-described embodiment functionis recorded as shown in FIG. 2, and reading and executing the programcode stored in the storage medium by the device of the system (CPU 301or CPU 6001). As a method of providing Client PC with the program ordata shown in FIG. 77, a method of providing PC body 7001 with floppydisc FD 7000 with the program stored therein as shown in FIG. 78 is alsogeneral. In this case, the program code itself read from the storagemedium realizes the function of the above-described embodiment, and thestorage medium in which the program code is stored constitutes thepresent invention.

As the storage medium for supplying the program code, for example, inaddition to the floppy disc or the hard disc, an optical disc, anoptical magnetic disc, CD-ROM, CD-R, a magnetic tape, a nonvolatilememory card, ROM, and the like can be used. Moreover, by executing theprogram code read by the computer, the function of the above-mentionedembodiment is realized, but additionally, based on the instruction ofthe program code, OS (operating system) operating on the computer, andthe like perform a part or the whole of the actual processing. Needlessto say, by the processing the function of the above-mentioned embodimentis also realized. Furthermore, after the program code read from thestorage medium is written in a memory mounted on a function expansionboard inserted into the computer or a function expansion unit connectedto the computer, based on the instruction of the program code, the CPU,and the like mounted on the function expansion board or the functionexpansion unit perform a part or the whole of the actual processing.Needless to say, by the processing the function of the above-mentionedembodiment is also realized.

FIG. 79 is a sectional view showing an inner structure of a laser beamprinter (hereinafter abbreviated as LBP) which can be applied to thelaser beam printer engines 103 and 104 of FIG. 1, and the LBP canperform printing on a recording sheet by the input of character patterndata, and the like. In FIG. 79, LBP body 8012 forms an image on therecording sheet as recording medium based on the supplied characterpattern, and the like. Numeral 8000 denotes an operation panel on whichan operating switch, LED display, and the like are arranged, and 8001denotes a printer control unit which entirely controls LBP 8012 andanalyzes the character pattern information, and the like. The printercontrol unit 8001 mainly converts the character pattern information intoa video signal and transmits an output to a laser driver 8002. The laserdriver 8002 is a circuit for driving a semiconductor laser 8003, andswitches on or off a laser beam 8004 emitted from the semiconductorlaser 8003 in response to the entered video signal. The laser beam 8004is swung horizontally by a rotating polygonal mirror 8005 to scan on anelectrostatic drum 8006. Thereby, an electrostatic latent image of acharacter pattern is formed on the electrostatic drum 8006. After thelatent image is developed by a developing unit 8007 around theelectrostatic drum 8006, the image is transferred to the recordingsheet. In the recording sheets, cut sheets are used, and the cutrecording sheets are stored in a plurality of sheet cassettes 8008attached to LBP 8012 for accommodating a plurality of types of sheets.The sheets are taken into the apparatus by a sheet feed roller 8009 andconveying rollers 8010 and 8011, and supplied to the electrostatic drum8006.

FIG. 80 is a diagrammatic view of an ink jet recording apparatus IJRAwhich can be applied to the ink jet printer engine 105 of FIG. 1. In thedrawing, a carriage HC is engaged in a spiral groove 9003 of a leadscrew 9004 rotating via drive force transmission gears 9010, 9008 withforward/reverse rotation of a drive motor 9011, has a pin (not shown),and is reciprocated/moved in directions of arrows a, b. On the carriageHC, an ink jet cartridge IJC is mounted. A sheet press plate 9001presses the sheet against a platen 9000 over a moving direction of thecarriage. Photo-couplers 9006, 9007 are home position detecting meanswhich confirm the presence of a carriage lever 9005 in this area andswitch a rotating direction of the motor 9011. A member 9013 supports acap member 9019 for capping a front surface of a recording head, andsuction means 9012 for sucking the inside of the cap performs suctionrecovering of the recording head via an opening 9020 inside the cap. Acleaning blade 9014, and a member 9016 which can move the blade back andforth are supported by a body support plate 9015. The blade is notlimited to this form, and needless to say, a known cleaning blade can beapplied to the example. Moreover, a lever 9018 starts suction for thesuction recovering, and moves as a cam 9017 engaged with the carriagemoves. The movement is controlled by controlling a drive force from thedrive motor by a known transmission means such as a clutch switchover,and the like. For the capping, cleaning, and suction recoveringoperations, when the carriage reaches an area on the side of the homeposition, a desired operation can be performed in the correspondingposition by action of the lead screw 9004. By performing the desiredoperation at a known timing, the operations can be applied in theexample.

As described above, according to the embodiment, by using the logicaldevice control program (scan job manager 419, print job managers 501 to509, copy job managers 601 to 608) retaining the function of the logicaldevice to which the job is transmitted from the information processingapparatus and managing the job transmitted to the logical device, andthe physical device control program (scanner controller 420, LBPcontrollers 510, 511, Ink Jet controller 512) retaining the function ofthe device engine of the peripheral and managing the job in the deviceengine, the job can be analyzed.

Here, the physical device control program is a scanner control program(scanner controller 420) which controls the scanner engine of theperipheral. The physical device control program is a laser beam printercontrol program (LBP controllers 510, 511) which controls the laser beamprinter engine of the peripheral. The physical device control program isan ink jet printer control program (Ink Jet printer controller 512)which controls the ink jet printer engine of the peripheral. Moreover,the logical device control program is a print job control program (printjob managers 501 to 509) which controls the laser beam printer controlprogram, or the ink jet printer control program, or the laser beamprinter control program and the ink jet printer control program of theperipheral. Furthermore, the logical device control program is a scannerjob control program (scan job manager 419) which controls the scannercontrol program of the peripheral. Additionally, the logical devicecontrol program is a copy job control program (copy job managers 601 to608) which controls the scanner control program and the laser beamprinter control program or the ink jet printer control program, or thelaser beam printer control program and ink jet printer control programof the peripheral.

By the configuration, the logical device control program can retain arelation with at least one device engine which is used by the logicaldevice to execute the job. Moreover, based on the job transmitted to thelogical device, the device engine to be used for actually executing thejob can be determined. Moreover, the function retained by the logicaldevice control program can be changed. The job transmitted to thelogical device can be associated with the job managed by the physicaldevice which actually executes the job, and managed. Additionally, thereare a plurality of logical device control programs, and by comparingload states of a plurality of logical device control programs, anoptimum logical device control program can be selected. Moreover, thereare provided a plurality of logical device control programs and ageneral program (Supervisor 410) which administers the plurality oflogical device control programs. In the general program, the subaddressand connection interface type used in transmitting the job to thelogical device control programs can be associated with the logicaldevice control programs and retained. Moreover, the general programretains a list of information indicating whether the subaddress is validor invalid. When the job is transmitted to the not-valid subaddress, thejob can be canceled. Furthermore, the general program retains a list ofauthentication information of a user who can use the peripheral, and cannotify an error of the job when the user information included in theinputted job is not included in the list of the authenticationinformation. Additionally, the general program can retain the list ofsecurity levels indicating types of authentication judgment processingsof users who can use the peripheral. Moreover, the logical devicecontrol program can retain a list of connection interfaces andtransmission addressees for transmitting event data to the informationprocessing apparatus when the event occurs during the job analysis.Furthermore, when the event occurs during the job analysis in thelogical device control program, the list of connection interfaces andtransmission addressees for the transmission to the informationprocessing apparatus is referred to and the event data can betransmitted.

Moreover, as described above, according to the embodiment, by judgingwhether or not the job script can be issued to the peripheral based onthe function obtained from the peripheral (MFP 201) (steps 5402 to 5404,5502 to 5504, 5602 to 5604), the job issuance processing can becontrolled in accordance with the judgment result.

Here, the attribute list (attribute table) indicating the functions ofthe physical device control program, logical device control program,resource control program (font manager 413, form overlay manager 414,log manager 415, color profile manager 416) and general program forsupervising the programs of the peripheral is obtained from theperipheral. Moreover, the combination of attributes in which the jobsetting is inhibited (attribute IDs 801 to 805) is obtained.Furthermore, the download job or the print job is issued to theperipheral. Additionally, the upload job or the scan job is issued tothe peripheral. Moreover, the job issuance method is selected inaccordance with the attribute (attribute ID 601) indicating thesupported download method of the obtained function and the location ofjob issuance target data. Furthermore, the job issuance method isselected in accordance with the attribute (attribute ID 602) indicatingthe supported upload method of the obtained function and the storedposition of job issuance target data. Additionally, the job issuancetarget data is print document data. Moreover, the job issuance targetdata is scan document data. Furthermore, the job issuance target data isfont data. Additionally, the job issuance target data is form overlaydata. Moreover, the job issuance target data is color profile data.Furthermore, the job issuance target data is log data. Additionally, thejob issuance target data is font data. Moreover, the event format datafor the event received from the peripheral is obtained, and the receivedevent is analyzed based on the event format data. Furthermore, the logdata of the peripheral and the log format data of the log data areobtained, and the log data is analyzed based on the log format data.Additionally, the charge data (count data) of the peripheral and theformat data of the charge data are obtained, and the charge data isanalyzed based on the charge format data.

Moreover, as described above, according to the embodiment, in accordancewith the function (attribute value) obtained from the peripheral, theuser interface of the control program for controlling the peripheral canautomatically be formed (step 4813). Furthermore, the display (FIGS. 81,82) of the user interface for the peripheral can be controlled inaccordance with the obtained function. Additionally, the information(attribute value) concerning the setting range of the function of theperipheral can be obtained. Moreover, the information concerning thesetting range is represented by the combination of attributes (attributeIDs 801 to 805) in which job setting is inhibited. Furthermore, theinformation (attribute value) concerning the function choices of theperipheral can be obtained. When the attribute list (attribute table)indicating the function of the peripheral is obtained from theperipheral, and the attribute ID of the attribute list is designated,the attribute value can be obtained. Additionally, the attribute list(attribute table) indicating the functions of physical device controlprogram, logical device control program, resource control program, andgeneral control program for supervising the programs of the peripheralcan be obtained from the peripheral. Moreover, the physical devicecontrol program is a scanner control program for controlling the scannerengine of the peripheral. Furthermore, the physical device controlprogram is the laser beam printer control program for controlling thelaser beam printer engine of the peripheral. Additionally, the physicaldevice control program is the ink jet printer control program forcontrolling the ink jet printer engine of the peripheral. Moreover, thelogical device control program is the print job control program forcontrolling the laser beam printer control program, or the ink jetprinter control program, or the laser beam printer control program andthe ink jet printer control program of the peripheral. Furthermore, thelogical device control program is the scanner job control program forcontrolling the scanner control program of the peripheral. Additionally,the logical device control program is the copy job control program forcontrolling the scanner control program and the laser beam printercontrol program or the ink jet printer control program, or the laserbeam printer control program and the ink jet printer control program ofthe peripheral. Moreover, the resource control program is the fontcontrol program for managing the font of the peripheral. Furthermore,the resource control program is the form overlay control program formanaging the form overlay of the peripheral. Additionally, the resourcecontrol program is the log control program for managing the log of theperipheral. Moreover, the resource control program is the color profilecontrol program for managing the color profile of the peripheral.

As described above, according to the present invention, in accordancewith the function obtained from the peripheral, the user interface ofthe control program for controlling the peripheral can automatically beformed. Moreover, in accordance with the obtained function the displayof the user interface for the peripheral can be controlled. Furthermore,the information (attribute value) concerning the setting range of thefunction of the peripheral can be obtained. Additionally, theinformation concerning the setting range is represented by thecombination of the attributes in which job setting is inhibited.Furthermore, the information concerning the function choices of theperipheral can be obtained. When the attribute list (attribute table)indicating the function of the peripheral is obtained from theperipheral, and the attribute ID of the attribute list is designated,the attribute value can be obtained. Additionally, the attribute listindicating the functions of physical device control program, logicaldevice control program, resource control program, and general controlprogram for supervising the programs of the peripheral can be obtainedfrom the peripheral.

What is claimed is:
 1. An information processing apparatus forcontrolling a peripheral via a communication interface and for issuing ajob to the peripheral, comprising: a function-identification obtaineradapted to obtain, via the communication interface, information thatincludes a list of at least one inhibited function of the peripheral,which function is inhibited from use in processing the job; a jobrestriction unit adapted to restrict issuance of the job in accordancewith the list of at least one inhibited function obtained by saidobtainer; and a controller adapted to automatically form a userinterface of a control program for controlling the peripheral inaccordance with the list of at least one inhibited function obtained bysaid obtainer.
 2. The information processing apparatus according toclaim 1, wherein the list obtained by said obtainer comprises aplurality of inhibited functions.
 3. The information processingapparatus according to claim 1, wherein said obtainer obtainsinformation concerning a setting range of a function of the peripheral.4. The information processing apparatus according to claim 3, whereinthe information concerning the setting range is represented by acombination of attributes in which job setting is inhibited.
 5. Theinformation processing apparatus according to claim 1, wherein saidobtainer obtains information concerning function choices of theperipheral.
 6. The information processing apparatus according to claim1, wherein said obtainer obtains an attribute list indicating a functionof the peripheral from the peripheral, and designates an attribute ID ofthe attribute list to obtain an attribute value.
 7. The informationprocessing apparatus according to claim 1, wherein said obtainer obtainsan attribute list indicating functions of a physical device controlprogram, a logical device control program, a resource control program,and a general control program for supervising the programs of theperipheral from the peripheral.
 8. The information processing apparatusaccording to claim 7, wherein the physical device control program is ascanner control program for controlling a scanner engine of theperipheral.
 9. The information processing apparatus according to claim7, wherein the physical device control program is a laser beam printercontrol program for controlling a laser beam printer engine of theperipheral.
 10. The information processing apparatus according to claim7, wherein the physical device control program is an ink jet printercontrol program for controlling an ink jet printer engine of theperipheral.
 11. The information processing apparatus according to claim7, wherein the logical device control program is a print job controlprogram for controlling a laser beam printer control program, or an inkjet printer control program, or the laser beam printer control programand the ink jet printer control program of the peripheral.
 12. Theinformation processing apparatus according to claim 7, wherein thelogical device control program is a scanner job control program forcontrolling a scanner control program of the peripheral.
 13. Theinformation processing apparatus according to claim 7, wherein thelogical device control program is a copy job control program forcontrolling a scanner program and a laser beam printer control programor an ink jet printer control program, or the laser beam printer controlprogram and the ink jet printer control program of the peripheral. 14.The information processing apparatus according to claim 7, wherein theresource control program is a font control program for managing a fontof the peripheral.
 15. The information processing apparatus according toclaim 7, wherein the resource control program is a form overlay controlprogram for managing a form overlay of the peripheral.
 16. Theinformation processing apparatus according to claim 7, wherein theresource control program is a log control program for managing a log ofthe peripheral.
 17. The information processing apparatus according toclaim 7, wherein the resource control program is a color profile controlprogram for managing a color profile of the peripheral.
 18. Aninformation processing method in an information processing apparatus forcontrolling a peripheral via a communication interface and for issuing ajob to the peripheral, comprising the steps of: obtaining, via thecommunication interface information that includes a list of at least oneinhibited function of the peripheral, from the peripheral which functionis inhibited from use in processing the job; restricting issuance of thejob in accordance with the list of at least one inhibited functionobtained in said obtaining step; and automatically forming a userinterface of a control program for controlling the peripheral inaccordance with the list of at least one inhibited function.
 19. Theinformation processing method according to claim 18, wherein the listobtained in said obtaining step comprises a plurality of inhibitedfunctions.
 20. The information processing method according to claim 18,further comprising the step of obtaining information concerning asetting range of a function of the peripheral.
 21. The informationprocessing method according to claim 20, wherein the informationconcerning the setting range is represented by a combination ofattributes in which job setting is inhibited.
 22. The informationprocessing method according to claim 18, further comprising the step ofobtaining information concerning function choices of the peripheral. 23.The information processing method according to claim 18, furthercomprising the steps of: obtaining an attribute list indicating afunction of the peripheral from the peripheral; and designating anattribute ID of the attribute list to obtain an attribute value.
 24. Theinformation processing method according to claim 18, further comprisingthe step of obtaining an attribute list indicating functions of aphysical device control program, a logical device control program, aresource control program, and a general control program for supervisingthe programs of the peripheral from the peripheral.
 25. The informationprocessing method according to claim 18, wherein the physical devicecontrol program is a scanner control program for controlling a scannerengine of the peripheral.
 26. The information processing methodaccording to claim 18, wherein the physical device control program is alaser beam printer control program for controlling a laser beam printerengine of the peripheral.
 27. The information processing methodaccording to claim 18, wherein the physical device control program is anink jet printer control program for controlling an ink jet printerengine of the peripheral.
 28. The information processing methodaccording to claim 18, wherein the logical device control program is aprint job control program for controlling a laser beam printer controlprogram, or an ink jet printer control program, or the laser beamprinter control program and the ink jet printer control program of theperipheral.
 29. The information processing method according to claim 18,wherein the logical device control program is a scanner job controlprogram for controlling a scanner control program of the peripheral. 30.The information processing method according to claim 18, wherein thelogical device control program is a copy job control program forcontrolling a scanner control program and a laser beam printer controlprogram or an ink jet printer control program, or the laser beam printercontrol program and the ink jet printer control program of theperipheral.
 31. The information processing method according to claim 18,wherein the resource control program is a font control program formanaging a font of the peripheral.
 32. The information processing methodaccording to claim 18, wherein the resource control program is a formoverlay control program for managing a form overlay of the peripheral.33. The information processing method according to claim 18, wherein theresource control program is a log control program for managing a log ofthe peripheral.
 34. The information processing method according to claim18, wherein the resource control program is a color profile controlprogram for managing a color profile of the peripheral.
 35. A storagemedium, which stores an information processing program executed in aninformation processing apparatus for controlling a peripheral via acommunication interface and for issuing a job to the peripheral, theinformation processing program comprising code for performing the stepsof: obtaining, via the communication interface, information thatincludes a list of at least one inhibited function of the peripheral,from the peripheral, which function is inhibited from use in processingthe job; restricting issuance of the job in accordance with the list ofat least one inhibited function obtained in said obtaining step; andautomatically forming a user interface of a control program forcontrolling the peripheral in accordance with the list of at least oneinhibited function.
 36. The storage medium according to claim 35,wherein the list obtained in said obtaining step comprises a pluralityof inhibited functions.
 37. The storage medium according to claim 35,wherein information concerning a setting range of a function of theperipheral is obtained.
 38. The storage medium according to claim 37,wherein the information concerning the setting range is represented by acombination of attributes in which job setting is inhibited.
 39. Thestorage medium according to claim 35, wherein information concerningfunction choices of the peripheral is obtained.
 40. The storage mediumaccording to claim 35, wherein the information processing programfurther comprises code for performing the steps of: obtaining anattribute list indicating a function of the peripheral from theperipheral; and designating an attribute ID of the attribute list toobtain an attribute value.
 41. The storage medium according to claim 35,wherein an attribute list indicating functions of a physical devicecontrol program, a logical device control program, a resource controlprogram, and a general control program for supervising the programs ofthe peripheral is obtained from the peripheral.
 42. The storage mediumaccording to claim 35, wherein the physical device control program is ascanner control program for controlling a scanner engine of theperipheral.
 43. The storage medium according to claim 35, wherein thephysical device control program is a laser beam printer control programfor controlling a laser beam printer engine of the peripheral.
 44. Thestorage medium according to claim 35, wherein the physical devicecontrol program is an ink jet printer control program for controlling anink jet printer engine of the peripheral.
 45. The storage mediumaccording to claim 35, wherein the logical device control program is aprint job control program for controlling a laser beam printer controlprogram, or an ink jet printer control program, or the laser beamprinter control program and the ink jet printer control program of theperipheral.
 46. The storage medium according to claim 35, wherein thelogical device control program is a scanner job control program forcontrolling a scanner control program of the peripheral.
 47. The storagemedium according to claim 35, wherein the logical device control programis a copy job control program for controlling a scanner control programand a laser beam printer control program or an ink jet printer controlprogram, or the laser beam printer control program and the ink jetprinter control program of the peripheral.
 48. The storage mediumaccording to claim 35, wherein the resource control program is a fontcontrol program for managing a font of the peripheral.
 49. The storagemedium according to claim 35, wherein the resource control program is aform overlay control program for managing a form overlay of theperipheral.
 50. The storage medium according to claim 35, wherein theresource control program is a log control program for managing a log ofthe peripheral.
 51. The storage medium according to claim 35, whereinthe resource control program is a color profile control program formanaging a color profile of the peripheral.
 52. An informationprocessing system comprising: a peripheral having a plurality offunctions; and an information processing apparatus for controlling theperipheral via a communication interface and for issuing a job to theperipheral, comprising: a function-identification obtainer adapted toobtain, via the communication interface, information that includes alist of at least one inhibited function of the peripheral, whichfunction is inhibited from use in processing the job; a job restrictionunit adapted to restrict issuance of the job in accordance with the listof at least one inhibited function obtained by said obtainer; and acontroller adapted to automatically form a user interface of a controlprogram for controlling the peripheral in accordance with the list of atleast one inhibited function obtained by said obtainer.
 53. Theinformation processing system according to claim 52, wherein the listobtained by said obtainer comprises a plurality of inhibited functions.54. The information processing system according to claim 52, whereinsaid obtainer obtains information concerning a setting range of afunction of the peripheral.
 55. The information processing systemaccording to claim 54, wherein the information concerning the settingrange is represented by a combination of attributes in which job settingis inhibited.
 56. The information processing system according to claim52, wherein said obtainer obtains information concerning functionchoices of the peripheral.
 57. The information processing systemaccording to claim 52, wherein said obtainer obtains an attribute listindicating functions of the peripheral from the peripheral, anddesignates an attribute ID of the attribute list to obtain an attributevalue.
 58. The information processing system according to claim 52,wherein said obtainer obtains an attribute list indicating functions ofa physical device control program, a logical device control program, aresource control program, and a general control program for supervisingthe programs of the peripheral from the peripheral.
 59. The informationprocessing system according to claim 52, wherein the physical devicecontrol program is a scanner control program for controlling a scannerengine of the peripheral.
 60. The information processing systemaccording to claim 52, wherein the physical device control program is alaser beam printer control program for controlling a laser beam printerengine of the peripheral.
 61. The information processing systemaccording to claim 52, wherein the physical device control program is anink jet printer control program for controlling an ink jet printerengine of the peripheral.
 62. The information processing systemaccording to claim 52, wherein the logical device control program is aprint job control program for controlling a laser beam printer controlprogram, or an ink jet printer control program, or the laser beamprinter control program and the ink jet printer control program of theperipheral.
 63. The information processing system according to claim 52,wherein the logical device control program is a scanner job controlprogram for controlling a scanner control program of the peripheral. 64.The information processing system according to claim 52, wherein thelogical device control program is a copy job control program forcontrolling a scanner control program and a laser beam printer controlprogram or an ink jet printer control program, or the laser beam printercontrol program and the ink jet printer control program of theperipheral.
 65. The information processing system according to claim 52,wherein the resource control program is a font control program formanaging a font of the peripheral.
 66. The information processing systemaccording to claim 52, wherein the resource control program is a formoverlay control program for managing a form overlay of the peripheral.67. The information processing system according to claim 52, wherein theresource control program is a log control program for managing a log ofthe peripheral.
 68. The information processing system according to claim52, wherein the resource control program is a color profile controlprogram for managing a color profile of the peripheral.